Blasphemy: The Case Against Ruby on Rails
alterlabs.com
alterlabs.com
I'm finishing off a consulting project now with Rails and everybody's happy. For my startup though we're staying with Python and the much lower level Pylons.
The one I do think needs some confronting is the "no throat to choke" argument. It's just silly: if you research any sufficiently popular tool, you'll find out what areas it falls short in. If you aren't able to work around the problem as easily as you thought, you'll end up with delays and bugs. With a vendor supported product, you can choke your vendor rep until he helps you solve your problem. This usually takes as long or longer than fixing it yourself, and the result is the same: your project is still late and buggy.
Yes a non-technical manager in a large corporation... that makes perfect sense to post this on ycombinator...
"given the framework, Its hard to separte Rails "the technology" from Rails "the movement" "
Umm only if you're not technical or too lazy to really study it (making half assed assumptions instead)... I really don't mind good critiques of rails (slow, lacking standard functionality, ...), but come on - this has got to be one of the most stupid article posted
" the key difference between a knucklehead java programmer and a knucklehead Ruby/Rails programmer is that the former can be found out much more readily (more peeps are familiar with java) than the latter."
(being a former java programmer) no offense but can you actually back this up with real numbers/case studies instead of pulling it out of your ass - like the author did?
Don't get me wrong there are good critiques of rails like from Bryan of likebetter or Django's creator, but this one is just near retarded.
A lot of the author's points you can find in other languages as well (such as pretenders in java or 'x' language), and most of it is just criticizing for either its popularity with startups or lack of enterprise adoption.
I just don't think the author has enough knowledge of either rails or ruby to really comment on it. (Ruby is a clean way of fast prototyping and it can scale if you replace the inefficient bottlenecks with inline C, ...)
Unfortunately he didn't say that in the article.
"Dude has also got an article supporting Rails as a choice"
I hate to be mean, but I hope it doesn't suck as hard as this article ala "rails is great because everyone in a startup is using it"
"both posts seem to come at it from a relatively non-techie perspective -- more from the Mgr view "
geared towards PHBs in a large stale corporation? Again I really fail to see the point of this post on ycombinator
Oh yeah something I forgot to mention - in terms of overcoming a rails app's inefficiencies/problems with scalability, there's also this magical thing called web services (REST, SOAP); you know a rails app could talk to a java or C based app on another server...