What is Java good for?
1 - 14 of 14 Posts
Java is a programming language. As a language, it has it's strengths and weaknesses. In terms of blu ray, the fact that blu ray supports an actual programming language means that developers have the ability to do some very complicated things in software. But it also means that the blu ray player has a lot of work to do to run the java programs on your blu ray discs, which can lead to slow performance like you're seeing on your player. Decks with more processing power available load much quicker- Dark Knight loads in less than 10 seconds or so on my PS3, for instance . . . . .
It is capable of doing things like graphics transparency, dual subtitles and changeable subtitle fonts; actually some of the stuff BD-J can do can also be done with HDMV - more details in the Blu-ray Disc Spec whitepaper. At present I think the lack of standards, programming level and hardware isn't up to it so I'd rather have simple disc that loads fast, plays and does resume play rather than over-fanciful menus.
Joined
·
2,099 Posts
All of the above, when it works like it is supposed to. In reality, Java is really only good for doing two things consistantly:
1) It has a talent for throwing exceptions when it comes across something it doesn't like, much like when any other programming language errors out. Java, however, goes one step further: Most other languages simply stop execution when a run-time error is encountered; Java crashes the entire server, requiring a reboot (this is what you see on the blu-ray player when it hangs and the only way out is to unplug the unit)
2) It is slower than sin, and the Blu-Ray implementation has absolutely no set of standards (thus the frequent FW upgrades); On the bright side, it is a hair faster than Applesoft Basic...
![]()
In a nutshell, the BDA would have had to work hard to make a worse choice for a platform to base Blu-Ray on...
1) It has a talent for throwing exceptions when it comes across something it doesn't like, much like when any other programming language errors out. Java, however, goes one step further: Most other languages simply stop execution when a run-time error is encountered; Java crashes the entire server, requiring a reboot (this is what you see on the blu-ray player when it hangs and the only way out is to unplug the unit)
2) It is slower than sin, and the Blu-Ray implementation has absolutely no set of standards (thus the frequent FW upgrades); On the bright side, it is a hair faster than Applesoft Basic...
In a nutshell, the BDA would have had to work hard to make a worse choice for a platform to base Blu-Ray on...
Joined
·
2,530 Posts
Vader,
I don't know who wrote the JAVA for your deathstar, but that's not how JAVA works in our shop.
A NULL pointer exception for example, can cause a stack trace dump, but I have yet to see it force a server reboot.
Now, if you want some exceptional crashes, you should try using old style C, with its pointers and the like. There I did manage to get the server to reboot...
![]()
I do agree that JAVA was not developed with BDs in mind and really has no place being on a disc. The BD world should really have looked at the way that SD DVD did theirs and pretty much stuck with that.
Seggers
Quote:
Originally Posted by Vader424242 /forum/post/15449290
All of the above, when it works like it is supposed to. In reality, Java is really only good for doing two things consistantly:
1) It has a talent for throwing exceptions when it comes across something it doesn't like, much like when any other programming language errors out. Java, however, goes one step further: Most other languages simply stop execution when a run-time error is encountered; Java crashes the entire server, requiring a reboot (this is what you see on the blu-ray player when it hangs and the only way out is to unplug the unit)
2) It is slower than sin, and the Blu-Ray implementation has absolutely no set of standards (thus the frequent FW upgrades); On the bright side, it is a hair faster than Applesoft Basic...![]()
In a nutshell, the BDA would have had to work hard to make a worse choice for a platform to base Blu-Ray on...
Vader,
I don't know who wrote the JAVA for your deathstar, but that's not how JAVA works in our shop.
A NULL pointer exception for example, can cause a stack trace dump, but I have yet to see it force a server reboot.
Now, if you want some exceptional crashes, you should try using old style C, with its pointers and the like. There I did manage to get the server to reboot...
I do agree that JAVA was not developed with BDs in mind and really has no place being on a disc. The BD world should really have looked at the way that SD DVD did theirs and pretty much stuck with that.
Seggers
It is good for nothing!!!. I am kidding, but there are problems using it on Blu-Ray disks.
It seems that quite a bit of processing power is necessary for JAVA to run and that is probably the reason why it slows things up. I wonder if they could have achieved the same results without using JAVA. HDDVD did not use it and the menus were much faster. Having said the above, I believe that future players will have greater processing power and it might also be possible to develop a JAVA light version to work on Blu-Ray players.
It seems that quite a bit of processing power is necessary for JAVA to run and that is probably the reason why it slows things up. I wonder if they could have achieved the same results without using JAVA. HDDVD did not use it and the menus were much faster. Having said the above, I believe that future players will have greater processing power and it might also be possible to develop a JAVA light version to work on Blu-Ray players.
Joined
·
2,099 Posts
I concur on all counts...
![]()
HD DVD used HDi, which ironically was co-developed by Disney. The "problem" with HDi was that it could not support BD+ (so the paranoid execs at FOX shot it down).
Quote:
Originally Posted by seggers /forum/post/15449389
Now, if you want some exceptional crashes, you should try using old style C, with its pointers and the like. There I did manage to get the server to reboot...![]()
I do agree that JAVA was not developed with BDs in mind and really has no place being on a disc. The BD world should really have looked at the way that SD DVD did theirs and pretty much stuck with that.
I concur on all counts...
HD DVD used HDi, which ironically was co-developed by Disney. The "problem" with HDi was that it could not support BD+ (so the paranoid execs at FOX shot it down).
Joined
·
312 Posts
Sony 's in bed with Java.Its called kickbacks.Amazing,this blu ray,better picture,better sound,larger storage,freakin slower load times.The slower load times are enough to turn people off to this format.Its perfect for people like Hugh Hefner,put in a movie,get laid and then watch the movie.
I don't understand why the studios don't just write a Java app that renders HDi. The could continue to use the HDi tools for menus and interactivity and access BD-J for those items that HDi just can't do. I suspect that Universal did just that, but haven't seen anything to back that up.
I don't understand why the studios don't just write a Java app that renders HDi. The could continue to use the HDi tools for menus and interactivity and access BD-J for those items that HDi just can't do. I suspect that Universal did just that, but haven't seen anything to back that up.
HDi, from the rival format, is not mentioned in the Blu-ray Disc spec so I rather doubt it. Isn't it making it more complicated? As I said, actually some of the stuff BD-J can do can also be done with HDMV, but I don't know if HDMV mode is simpler and quicker.
HDi, from the rival format, is not mentioned in the Blu-ray Disc spec so I rather doubt it. Isn't it making it more complicated? As I said, actually some of the stuff BD-J can do can also be done with HDMV, but I don't know if HDMV mode is simpler and quicker.
1 - 14 of 14 Posts
Join the discussion
