4 ms·
Using the CLR "future proofs" it. The iPhone can't use another processor without recompiling all the apps, but Windows Phone is processor independent. Not that
by bensummers 17y ago
Using the CLR "future proofs" it. The iPhone can't use another processor without recompiling all the apps, but Windows Phone is processor independent.
Not that it really matters as it looks like the ARM monoculture is going to continue for a while. At least ARM is a sensible architecture, unlike the power-sucking monstrosity that is x86 and the hardware to support its weird and wonderful instructions.
- malkia 17y agoJava has been like that since a long time, and yet it's problematic on small devices. CLR or compiled code is not the issue here - it's the hardware - resolution, number of buttons - that stuff. For games - compiled code and no garbage collecting might be better, but it's doable with CLR too (and actually I preffer CLR with JIT on the device more than compiling).
- rbanffy 17y agoJ2ME comes from a time when people imagined phones based on lots of very different architectures and code that would be seamlessly portable between vastly different devices. This is not how it turned out (at least not for now).
- rbanffy 17y agoIn reality, if there is no processor fast enough to run an application on top of a virtual machine with speed that is comparable to other platforms, the app is "present-proof". It may run well in the future, but, by then, what's the point?
- bensummers 17y agoThe compilation doesn't have to be on the device. The CLR has always supported ahead of time compilation. What if Microsoft's App Store did the compilation before it was downloaded to your device?