5 ms·
He seems to have preferred the 'momentum' and quality of the Rhino codebase over Jython - although he admits Jython might have seemed like the right choice at f
by r7000 19y ago
He seems to have preferred the 'momentum' and quality of the Rhino codebase over Jython - although he admits Jython might have seemed like the right choice at first glance. See the section about 3/5ths down.
- tx 19y agoI'd argue that there are at least two other MORE important factors: JS (IMHO) is somewhat closer to Ruby, compared to Python. In fact I suspect that his "secret 20% project" is Ruby to JS compiler (or vice versa) Also, (most importantly) using the same language for server AND client development is big-big win. He's been dreaming of a universal "web platform" which allows you to have real development process: pieces of you app here and there, and you freely move them around, executing server or client side, whatever works best for you at the moment. Because right now you have this huge stack of things to keep bookeeping for: HTML/CSS/JS/Ruby/SQL, all sitting in their own little files with their own little syntax. At least he got last 3 merged into one solid JS framework.
- staunch 19y agoNext Big [Development] Environment? Okay, I'll stop.