3 ms·
Seems to me they would apply to Javascript though, and that got quite fast with V8.
by nikbackm 13y ago
Seems to me they would apply to Javascript though, and that got quite fast with V8.
- dragonwriter 13y agoBeing the one widely supported client-side language for the web means that lots more money has been poured into making JavaScript implementations effective than has gone into Ruby (I wouldn't be surprised if Google put more resources into V8 than have gone into all Ruby implementations combined.)
- danneu 13y agoFor example, Lars Bak (virtual machine master) is the head programmer of V8. http://en.wikipedia.org/wiki/Lars_Bak_(computer_programmer) http://en.wikipedia.org/wiki/Lars_Bak_(computer_programmer)
- nikbackm 13y agoTrue, but since V8 is open-source, shouldn't it now be possible for the Ruby developers to borrow the techniques from it that made Javascript so much faster?
- dragonwriter 13y agoRuby isn't JavaScript. Studying V8's solutions to particular problems with making JavaScript efficient may help people seeking to make an efficient Ruby implementation, but how much is easily transferrable I don't know.
- vidarh 13y agoNone of the techniques that's gone into V8 are all that novel. Most of them - at least the ones that are relevant to Ruby - stems from research around Smalltalk and Self that's been well known for a very long time. The hard/time consuming part is implementing them.
- stiff 13y agoNo doubt V8 is much more mature than MRI, I think some language considerations do still apply though, JavaScript doesn't have method_missing, problem #5 doesn't apply, I guess there is more.