Re:Moving from PHP to C saved my web startup.
by sedachv on Friday October 22, 2010 @08:45PM
(#1822127)
I didn't know that, I thought everything ran on beam. I guess the point is the canonical Ruby implementation is really slow when it doesn't need to be. It's not like it's a hard problem, or even that it hasn't already been solved (look at GemStone's Maglev: http://ruby.gemstone.com/)
[ Parent
| on HN ]
Re:Moving from PHP to C saved my web startup.
by silentbicycle on Friday October 22, 2010 @10:53PM
(#1822420)
I've stopped commenting about MRI entirely, it just makes people mad, and it's not even fun anymore. It's too easy. Still, I have to give Matz credit for making a language a lot of people sincerely love.
I know it's splitting hairs whether bytecode + a VM counts as compiled or interpreted (it's both, really), but compiling to bytecode rather than a pure interpreter usually makes enough of a difference performance-wise that it's worth giving some credit.
Re:Moving from PHP to C saved my web startup.
by chc on Saturday October 23, 2010 @02:41AM
(#1822842)
If people would just stop talking about Ruby 1.8, it wold allow for more meaningful discussion. 1.9 is a lot faster and has better support for concurrency.
Re:Moving from PHP to C saved my web startup.
by silentbicycle on Saturday October 23, 2010 @07:38AM
(#1823264)
Indeed, it's too bad that the transition has been taking so long.
Re:Moving from PHP to C saved my web startup.
by Locke1689 on Saturday October 23, 2010 @02:45AM
(#1822848)
FYI, compilers are written completely different from interpreters. Bytecode languages are compiled as well.
Re:Moving from PHP to C saved my web startup.
by silentbicycle on Saturday October 23, 2010 @02:26PM
(#1824040)
I know, but often when people make that distinction, it's concerned with what performance ballpark the language has rather than strictly implementation issues.