5 ms·
> better That's it. The VMs on the market at the time we're absolutely terrible for phones. John Carmack was commenting on how JavaME gave you worse performa
by monocasa 9y ago
> better
That's it. The VMs on the market at the time we're absolutely terrible for phones. John Carmack was commenting on how JavaME gave you worse performance than an original IBM PC, and HotSpot's strategies absolutely destroy battery life.
- pjmlp 9y agoExcept that wasn't the only approach available. There are OEMs selling commercial JDKs for embedded use, with their own VM, JIT and AOT compiler variations, and library extensions. Contrary to Google, they always played by the rules.
- monocasa 9y agoIn 2008, none were as good as Dalvik for the use case.
- pjmlp 9y agoThat's the story Google likes to sell. Nokia and Sony-Ericsson flagship phones were quite good.
- monocasa 9y agoNo they weren't, I developed for them.
- pjmlp 9y agoMe too, alumni from that little company located in Espoo.
- monocasa 9y agoI was third party. Maybe your close association is blinding you.
- geodel 9y agoI hope that little company does not come under pressure to make Android phones.
- pjmlp 9y agoIt is hard to compete against a free beer OS originally developed with tech unlawfully taken from other companies. So one either swims or joins the graveyard of companies that tried to fight it.
- monocasa 9y ago> It is hard to compete against a free beer OS I'd argue that it's next to impossible. OSes are a commodity now. Even Microsoft is coming around to that idea. > tech unlawfully taken from other companies. All of the previous caselaw said that this was fine.
- carussell 9y agoThe whole subthread focusing on the Android VM is completely irrelevant. The entire argument at this point has to do with the inclusion of the Java APIs. Not even Oracle or the appeals court are harping on Google's custom VM.
- pjmlp 9y agoThe VM is used as an excuse by Google supporters why they should get excused to help drive Sun into the floor. Java still exists today thanks Oracle, not Google.
- deleted 9y ago[deleted]
- Zigurd 9y agoAndroid does not have a Java VM, and it does not run Java bytecode. Dalvik bytecode is more compact, and more CPU efficient, and the more recent ART runtime is even more efficient and performant. But it isn't a JVM.
- pjmlp 9y agoJust like all the vendors selling commercial JDKs for the embedded market. They also offer customized versions fine tuned for their deployment scenarios, doing Java bytecode to either native (AOT) or their own proprietary bytecode format when generating the firmware image. Or for example, IBM Java running on IBM i mainframe, where Java bytecodes used to be translated into the TIMI bytecodes, just like any other IBM i application.
- Zigurd 9y agoThe Dalvik and ART runtimes differ in that the do not run Java bytecodes. Every commercial embedded jvm, open source jvm, and me jvm I have seen all run Java bytecodes and you can use any toolchain that makes .jar files with these vms. Unless the translation you mention can happen at runtime, it isn't a jvm.
- pjmlp 9y agoIt happens at deployment time, as mentioned. Firmware does not change during runtime.
- deleted 9y ago[deleted]