On Wed, Nov 17, 2010 at 8:09 PM, Kevin Wright <kev.lee.wri...@gmail.com>wrote:
> > > 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. >> >> > This is equivalent to saying that the JVM running on an ARM system needs > to do so via an x86 emulator. A totally insane idea! > > Instead, we have the JVM, mono, parrot, LLVM, etc. each abstracting away > from the underlying architecture and targeting each platform directly. This > approach is no different to a language being able to target multiple VMs - > the techniques to work with multiple instruction sets in bytecode are > fundamentally no different from the techniques for targeting multiple > instruction sets in hardware. > But with one bytecode set being translated to another and then natively compiled to native code means a lot of time is getting wasted. Emulating the different semantics of the vm lifecycle also means more emulation and more wasted cpus...Nothing is free. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
