3 ms·
Having skimmed it, I can reduce the 11,500 words to just 128: -- The future lies with dynamic languages; their success in big systems, and Scala as a complex
by gojomo 18y ago
Having skimmed it, I can reduce the 11,500 words to just 128:
--
The future lies with dynamic languages; their success in big systems, and Scala as a complex move in the anti-dynamic direction, are both inconvenient developments for Java and static-typing orthodoxy. Still, the JVM and VMs in general are good for dynamic language implementations.
Javascript/Rhino is better than you think, and among the best of the JVM languages -- better than Java, and still easy to integrate with Java in both directions. Rhino is getting investment from Google and elsewhere; remaining objections will be conquered.
Google will open-source 'Rhino's not Ruby' (aka 'Rhino on Rails') this year (he hopes). RnR has been used by a 20-developer team there to build a huge web app in a small code footprint. Google's JSCompiler for compressing JS will likely be open-sourced, too.
- anewaccountname 18y agoI'd change that to: "to build a huge web app that never saw the light of day"
- andreyf 18y agoStill, the JVM and VMs in general are good for dynamic language implementations. Not just good, but vital for just-in-time optimization. The argument of JIT bringing dynamic languages to the speeds of Java/C++ seems compelling...