Steve Blackburn wrote:
A quick recap on key points from my original post (below):
. Focus on componentization
. Use one or two existing VMs to bootstrap and drive effort to componentize
. Concurrently develop new cores
As far as I can tell the goal of componentization is widely accepted.
I view the VM core as another component, one of the simplest, but most
design critical. The model of componentization allows any component to
be written in whatever language makes most sense.
For the sake of momentum I advocate concurrently pushing
componentization in one or more existing VM cores while developing new
cores.
In my experience our biggest challenge is going to be in getting
componentization to work. We've pushed this hard with MMTk (getting it
to plug into multiple VMs, across language boundaries), and since the MM
is probably the most intricately connected component, that gives us hope.
You may find it interesting to read the writeup of the ORP team's effort
to port their GC & JIT to Rotor
(http://www.jot.fm/issues/issue_2004_10/article3/index_html).
I'm pretty sure we want a framework in C/C++, whatever components are
developed in.
Umm. Why?
So it can run everywhere.
--
http://www.apache-ssl.org/ben.html http://www.thebunker.net/
"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff
