Originally Posted by gsa700
You guys are probably right. I do know the Linux kernel isn't java.
However, I've been around a while and I tell you that anytime you see Java and end user application in the same sentence, it equals slow buggy apps. And they look like crap too. Even the fonts in the apps look bad because they don't use the system font renderer, Java apparently has it's own for portability.
See Adobe CS apps for java sucking.
Personally not the biggest fan of Java, If you ever used the PMS called Opera then you know how buggy a java based app can be.
Pretty much need to close IE on the machines atleast once a day to close the java VM, as Opera itself runs on a app server and you need to use IE to launch it on a terminal.
Though Java was a smart choice for Google.
You can port Android to any platform and still have the apps work without needing to recompile.
So really you could buy a windows 8 tablet toss android on it and still be able to use all the android apps you want as well as windows apps.
These days Java is just as good as .net
Originally Posted by steelbom
There's more to "64-bit" than that. Also there were appreciable improvements between Leopard (32-bit) and Snow Leopard (64-bit) and the same should be true of iOS 6 and iOS 7.
While some applications could benefit from 64bit even if it isn't using more then 4gb, most simply will not or not enough to warrant the extra development cost/time. Plus 64bit apps are not backward compatible so anyone stuck on a 32bit chip cant use it.
Difference between Leopard and Snow Leopard are more then just a simple evolution to 64bit, they cut down overall footprint of the OS and optimized parts of the OS. Kinda like windows 7 was a optimized vista. 64bit still is more suited for apps that need to use more then 4gb, your mostly wasting your time/money as a dev ATM adopting 64bit if you don't need it.Edited by DzillaXx - 9/11/13 at 5:51am