3 ms·
>Dalvik isn't fragmented at all As someone who admittedly isn't an Android developer, isn't the point that Dalvik's very existence has fragmented the Java ecos
by jaredsohn 15y ago
>Dalvik isn't fragmented at all
As someone who admittedly isn't an Android developer, isn't the point that Dalvik's very existence has fragmented the Java ecosystem? That's how I read the GP comment.
- bad_user 15y agoisn't the point that Dalvik's very existence has fragmented the Java ecosystem Yes and no. Dalvik is not Java, being a totally different VM, just as .NET's CLR is. And just as .NET's CLR, you can transform Java's bytecode to Dalvik bytecode by means of a compiler. The equivalent project in the .NET world would be IKVM, which allows you to transform Jars into .NET dlls. It is true that Google relies on the Java ecosystem for fueling Android ... they rely on Eclipse for IDE support, they rely on Harmony for the base classes and so on. But everybody working with Android knows that Dalvik is not Java and that Java libraries that are doing bytecode manipulations do not work on Dalvik out of the box, because Dalvik is not a JVM. So really, Dalvik is fragmenting Java in the same way .NET did.