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...
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.
Originally Posted by rwestley /forum/post/15449911
HDDVD did not use it and the menus were much faster.
Originally Posted by Vader424242 /forum/post/15450140
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).
Originally Posted by webdev511 /forum/post/15454944
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.