Vms that host both for example the CLR and JVM is nonsense due to the way each handles classloading for starters. They also use different byte codes, which would mean one or both would need to be emulated/translated into the instruction set of the other. What you are proposing has never happened in the cpu business, even when the Mac left 68000 and started to use power the older system had to be emulated. There is no previous example when two different systems with different instructions set somehow coexisted as first class citizens on a new execution environment.
I dont think many will be happy to adopt a system such as you mention (think like IKVM in mono land ) where their application is emulated inside another emulated system. Im no expert but having a double layered system of emulation must be quite slow no matter how great jit/aot becomes. Why would anyone trust Parrot ? If you thought Java 7 was slow look how long it took for Parrot to get their first release out... Do you really want to trust the world of computing on something that is that slow to in terms of evolution and proven ability to deliver on time ? -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
