Dalvik vs Mono
koushikdutta.com
koushikdutta.com
I must command the bloke who wrote the article but he should have provided more details like how he performed the tests and benchmarks.
Last Dalvik was designed to work on low resources ARM devices, it can probably be ported to run on x86 systems, but it won't take their full advantage. Mono wasn't designed specifically for that purpose (running on a low resources device) which makes Dalvik a better solution. I'll give an example take a proper 4x4, an AWD SUV, and a Sedan. The 4x4 will go anywhere and will prove to be a great instrument in exploring the off road, on the highway it will suffer from low grip, terrible handling, a low gas mileage. An SUV can be taken off road, but isn't capable to pass hard terain, while on the highway it will go better then a 4x4. A sedan will do well on the highway but taking it down to the beach can result in a misfortune.
Where's the evidence? The purpose of the post is that the author could not find any.
And really, a car analogy? On HN?
Mono was designed to port the .NET to other platforms
Either way, I remember reading that Dalvik (or, well, Java) was chosen for the constraints it places on the programmer and access to verification tools? Security or some such?
I guess its a tradeoff - to a user a JITed app would appear a bit slow at first, but get faster the more you use it (plus you would then need to probably persist the JIT codes, as you close/open apps all the time in android) which has more complexity. A fast runtime like dalvik is the same speed pretty much all the time.
Yes, it is conventional wisdom, but I am not sure if phones are as fast as we think yet. Sure my iphone runs at what, 450Mhz ? which is quick, but we may forget that JIT'ing of client side apps only recently became fast enough (at least to my taste).