Ruby on Rails Fails

Oh look, I rhymed!

"I'll add one more thing to the people reading this: I mean business when I say I'll take anyone on who wants to fight me. You think you can take me, I'll pay to rent a boxing ring and beat your fucking ass legally. Remember that I've studied enough martial arts to be deadly even though I'm old, and I don't give a fuck if I kick your mother fucking ass or you kick mine. You don't like what I've said, then write something in reply but fuck you if you think you're gonna talk to me like you can hurt me.

I'll never be afraid of some pilsner fresh fat fuck who eats donut hamburgers and only gets exercise when he plays World of Warcraft on a DDR pad."

Source: zedshaw.com

Okay, yeah, that was funny, but down to seriousness. I'm a PHP/Perl guy, obviously. I have used Rails, and in theory it IS better than PHP. However, Rails is a buggy, over-hyped, and immature framework. Rails has some great ideas, but they unforunately fail in the end because of elitist asshats. To them, if something doesn't work, you're just doing it wrong and have to ass-kiss Ruby and sacrifice a fucking goat to make it work correctly. With PHP, you can get exactly what you need and no more. It's like comparing an Apple to a Whopper.

Sure, Rails is superior to PHP in theory, but Rails has shitty library support. PHP might be ugly as sin, but it works, and works damn well. There is a reason languages like PHP and Perl are so successful: standards, standards, standards, and standards. Oh yea, and excellent support, be it community, plugins, libraries, or frameworks. Rails has no support, and has horrible library/plugin support, and is itself a framework.

RoR's claim to fame is rapid development. However, if you write a content management system in 30 minutes from "scratch", and something breaks on the business end, you're pretty much screwed since you didn't actually write any code. Plus, there are MVC frameworks for PHP, Perl, and just about every other language known to man, and they are written in whatever language you're developing in, so you actually know how to dig in and get your hands dirty.

Rails is a great idea, and I've learned many things from it, but in the end, I'm sticking with PHP. There is absolutely nothing Rails can do that PHP can't do just as well, if not better.

I apologize in advance for this post's formatting though. I'm scatterbrained tonight.