3 ms·
Your second paragraph illustrates the issue with lumping ruby and lisp together. Lisp is already fast, in some common lisps (e.g. sbcl) you have a compiler tha
by ska 12y ago
Your second paragraph illustrates the issue with lumping ruby and lisp together.
Lisp is already fast, in some common lisps (e.g. sbcl) you have a compiler that gets within about 2x of a good optimizing c compiler, which is pretty good. So in some sense, it already has the best of both worlds (more powerful than a ruby or python, faster than most languages when compiled).
I think the reasons it did't take over the world have nothing to do with the technical core, and everything to do with ecosystem and network effects.
- vinceguidry 12y agoI've a hunch that the speed of those flavors of Lisp is coming from a bunch of really smart people basically spending their entire careers optimizing it. Which gives me hope that Ruby can get there too. > ecosystem and network effects. Which is a really important consideration. Technologies are a dime a dozen, community is rare and ephemeral. If you can build a solid, robust community around your tech, it doesn't matter what the limitations are.
- ska 12y agoActually most of these compilers have pretty small teams, and in some cases part time volunteer effort has done a lot of the optimizer But language design really matters, for example one guy put together a JIT for lua that is roughly as fast as the JVM. He's good at it, but he wouldn't have been able to do the same thing with Java (or, I expect ruby) on his own....