2 ms·
True...Optimizing for getting to that popularity level fast is the wise thing to do, and so the most productive tool to develop in is the best one. But...there
by SwellJoe 20y ago
True...Optimizing for getting to that popularity level fast is the wise thing to do, and so the most productive tool to develop in is the best one.
But...there are major costs to a lack of reliability, and they can rear their head before you reach that level of popularity. If you're not able to stay up during that all important first crunch or slashdotting or digg...you won't ever make it to the sustained popularity and growth that requires scaling up. RoR does seem to have some problems with that.
Ruby is the slowest of the most popular scripting languages, by most measures. RoR is pathological with databases in some circumstances (not common cases, admittedly). And, from what I can tell most RoR stacks (Apache+fcgi, Mongrel, ngenix, Lighty, etc.) have one or more pretty serious flaws when scaling up.
I'd still consider using it, since it's so much damned fun to write Ruby code.