As far as this paper goes, the main idea is pluralism. Much software lore leans quite heavily on grand narratives about how things "should be done". The "postmodern" view is a reaction against that: in favour of…
Not sure whether you're disagreeing with the paper or the commenter's summary of it. As you could probably guess from the title of the paper, the goal is not a new "fully general" VM. An analogy I sometimes use is…
True that the CLR is not mentioned by name, but it is covered. I invite you to read the text again, and especially the following bit. "Specifically, we should aspire to package language implementations in a way that…
Good question. I agree that endless muddling has shown remarkable mileage. liballocs is not quite there yet, but is progressing (er, when I get time, which is not often enough). Beyond that, adoption is cultural. We…
Ouch. :-) There's a lot more to it than that, though wrapping malloc is certainly one part of it. (Reminds me I should finish my blog post on why wrapping malloc reliably is way harder than it should be.) But the key…
Thanks! Indeed I should have said "no more difficult to maintain than V8 in general... i.e. well beyond a researcher's means".
An important bit of context is that this is a talk from the workshop "MoreVMs", which is about -- you guessed it -- language VMs and not systems VMs. In that context, the qualifier is not necessary. In more general…
Indeed, it's Nimbus Roman. I did nothing special -- the SIGPLAN template did it for me. I had been assuming it just did \usepackage{times} internally, though on inspection it does seem to be doing…
As far as this paper goes, the main idea is pluralism. Much software lore leans quite heavily on grand narratives about how things "should be done". The "postmodern" view is a reaction against that: in favour of…
Not sure whether you're disagreeing with the paper or the commenter's summary of it. As you could probably guess from the title of the paper, the goal is not a new "fully general" VM. An analogy I sometimes use is…
True that the CLR is not mentioned by name, but it is covered. I invite you to read the text again, and especially the following bit. "Specifically, we should aspire to package language implementations in a way that…
Good question. I agree that endless muddling has shown remarkable mileage. liballocs is not quite there yet, but is progressing (er, when I get time, which is not often enough). Beyond that, adoption is cultural. We…
Ouch. :-) There's a lot more to it than that, though wrapping malloc is certainly one part of it. (Reminds me I should finish my blog post on why wrapping malloc reliably is way harder than it should be.) But the key…
Thanks! Indeed I should have said "no more difficult to maintain than V8 in general... i.e. well beyond a researcher's means".
An important bit of context is that this is a talk from the workshop "MoreVMs", which is about -- you guessed it -- language VMs and not systems VMs. In that context, the qualifier is not necessary. In more general…
Indeed, it's Nimbus Roman. I did nothing special -- the SIGPLAN template did it for me. I had been assuming it just did \usepackage{times} internally, though on inspection it does seem to be doing…