Live data from Hacker News

One VM to Rule Them All [pdf]

lafo.ssw.uni-linz.ac.at

1–10 of 90 posts

Re: One VM to Rule Them All [pdf]

#2
I couldn't gather much additional information from the slides, but do I understand this correctly that this substrate vm is an alternative jvm implementation that is faster and requires less memory? Would it be possible to port the usual jvm projects like Clojure or Scala to this in order to claim the same speed/memory gains as the described ruby implementation?

Re: One VM to Rule Them All [pdf]

#7
This looks interesting, but I am generally worried about something being owned by Oracle. Simple example; I own an Openpandora. I wrote a live coding environment in Java with a very basic, lispy language at it's core. Using any free Java implementation it either; did not start (core dump; suspect; not enough memory to get even the VM up) or ran very (unusable) slow. With the Java 7 closed source ARM version from Oracle; runs fast (just as smooth as on my Macbook) and uses very little memory.

I have the same experience on x86, but because of the abundance of resources it's less noticable.

I don't insist on everything being open source (completely), but base languages/VMs should be. Unless something about this changes, I'm not using anything owned by Oracle again.

Re: One VM to Rule Them All [pdf]

#8

I couldn't gather much additional information from the slides, but do I understand this correctly that this substrate vm is an alternative jvm implementation that is faster and requires less memory? Would it be possible to port the usual jvm projects like Clojure or Scala to this in order to claim the same speed/memory gains as the described ruby implementation?

The speed / memory gains seem to be because of optimising away the dynamic type overhead.

So Clojure yes but Scala, no.

Re: One VM to Rule Them All [pdf]

#9
This is amazing.

First because it means we can have _fast_ versions of existing languages.

Second because we can interact with the _huge_ amount of JVM libraries (this is a very big deal).

Third because SubstrateVM seem to be enabling the things I really like about Go: low memory footprint, fast startup time, and easy deployment (give me a binary that does everything I need).

They just need to make sure native interop is easy (both C and C++), and we have a winner!

Post reply on HN