Comments on: I Hate Ruby on Rails

By: Whiners

Whiners — Tue, 13 Jul 2010 19:20:46 +0000

What a bunch of whiners…WHAAAA, moobie-boobie don’t like Ruby!

By: Felipe

Felipe — Mon, 14 Dec 2009 05:56:50 +0000

What I really hate about Ruby on Rails is all the hype. Ho, it is so simple to write a CRUD application! You fucking morons. How hard is it really to write a CRUD app in any decent framework that is not ROR. You have to be an idiot to find it in hard in Java or .NET. Go and suck a lemon you Ruby loving assholes.

Stay classy, Felipe

By: Nathan

Nathan — Sat, 17 Oct 2009 02:32:19 +0000

I'm going to join the few voices here, and say Ruby and Rails suck a fat one. Went in with an open mind (I program in a lot of languages and frameworks), spent a year with a 100% Ruby on Rails only company, hated it with a passion. It's called "rails" for a reason - you can only go ONE direction.

Why do I write anything when nobody bothers to read it

By: Danny

Danny — Sun, 12 Oct 2008 01:47:21 +0000

This might not be strictly accurate, but as I see it there are two main classes of procedural languages, not in the way they work but in the way they actually LOOK on the screen. And which one you prefer now influences which languages you will prefer in future. In the first camp, there are the flexible languages, full of symbols, usually loosely typed to some degree, and for some reason usually written entirely in lower case – languages like Perl, Ruby, and to some extent PHP. In the second, you have the verbose languages which on the face of it at least are backed by well structured and very neatly documented libraries and APIS – languages like Java and CSharp. I’ve got a hunch that people make up their mind about a new language in about 10 seconds, and it’s to do with which camp they grew up in.

Editor: In other words – there are Unix languages (loosely typed, lots of symbols, poor documentation) and Windows languages (documented, IDEs, etc.). I definitely prefer the Unix ones.

By: Jon

Jon — Tue, 09 Sep 2008 13:56:39 +0000

Some of these comments just make me laugh. Seriously… if you can’t get RoR to work, what the hell are you doing in web development?

By: Asad Siddiqi

Asad Siddiqi — Mon, 09 Jun 2008 20:21:05 +0000

I read a tutorial on Rails which was on ONLAMP.com and saw couple video tutorials on you tube. The features and everything the technology promises is great. I tried to download/install/configure and get going and then i realized there is no proper documentation and they keep on breaking the existing stuff !! so the tutorials dont work !! the did that with dynamic scaffolding , it ticked me off , why would you wanna change things are done and break existing ways ?? I just cant understand that !!
It occurs to me that the Ruby Developers are very sharp, intelligent and perfectioniust developers but they suck at how they can keep it more workable and promote it !! I guess its certainly not the way to go !! They cud have done a lot better with the ideas they started with !!

By: Ian

Ian — Fri, 22 Feb 2008 22:46:40 +0000

I come from a C#/ASP.NET, classic ASP, and Java/JSP background. I literally want to delete ruby on rails. I hate it with an unimaginable passion. It is unbelievably awful. After reading the comments from most of the people that have replied to the original lame blog entry I feel much better though. Honestly, I thought there was something wrong with me; I have a Ruby book, and two Rails books, and development is so slow and so difficult I really thought I must be doing something wrong. Sure the examples in the agile book are great, and easy, but the moment, and I meant THE MOMENT, that you try to do something outside of those examples everything turns to crap. RoR makes it damn near impossible to implement the simplest of things. Not to beat a dead horse here, but like everyone else has said, where the heck is the documentation. Need something that’s not in the book, GOOD LUCK. You either have to figure it out yourself, or wait weeks in a forum (because nobody uses RoR) for someone that has struggled with the same problem that you are having to tell you that to fix the problem he switched to PHP, JSP, or ASP.NET. I HATE RUBY ON RAILS. PEACE OUT.

By: Lauren-Noelle

Lauren-Noelle — Sat, 17 Nov 2007 19:17:00 +0000

Oh the link here is only hosted, not a script, because I wanted my WP-related blog posts to be IN the wp community. I DO code my own websites.

My THING is doing it all with WP and plugins. My domain for it isn’t ready yet (neither is that blog).

Oh and I hate how the “anti” post was fictitious. Ugh. Self-important poo, it is.

By: Lauren-Noelle

Lauren-Noelle — Sat, 17 Nov 2007 19:15:06 +0000

I hate it. I hate it and I hate it’s face!

I have very limited experience, but it makes me sick to my stomach. It melted my brain having to use SSH!

I dealt with the beginnings, the the whole darn process ahead was frightening me. Working on it for 1.5 hrs drained me of all my energy, yet left me wired and crying for mommy. I have to keep running Linux commands the whole time? What? One site said THAT is “railsy”. Ugh.

Maybe I got the wrong impression, but there isn’t ANY info for ACTUAL newbies. I want ROR For Dummies, people.

I’m just a WordPress user, fairly new at PHP, but I kept reading about how great this thing was. They made it sound EASY!

It is 100% for computer geeks so computer geeky they should have government intelligence blasted into their genius brains. (I love Chuck. )

I hate it, an I hate its self-important face!

By: Daniel Rivera

Daniel Rivera — Fri, 13 Jul 2007 21:24:16 +0000

I have very mixed feelings about Rails. Sure, it is very speedy, can be very efficient, yadda yadda yadda. Maybe its my lack of experience with the language, but I do find that doing some chores takes me the longest time.

Also there are the caveats and gotchas that I hate. I created a rather simple CRUD application using AjaxScaffold and got it working in virtually no time. Then came adding security here and there and the whole thing got a bit tedious, but still doable. Couple of months after deployment I get a call from the customer, saying the application isn’t even booting up. WTF? I check the logs and keep getting some obscure error. After searching high and low for a cure, I find out that my gems updated themselves and broke the application. Solution is fairly easy and I learn about freezing applications. And I know that if I had put some settings here and there, it would have been avoided. But still, WTF? The application gets all crappy because these guys cannot make components backward compatible?

And even further, the logs kept showing some warning messages: this and that feature should not be used and will be removed from the next version (i.e. either freeze the application NOW or your application will surely DIE).

I love the whole gem thing, installing from the command line and getting to work without having to browse thru a million jar files, and I love the simplicity of the language itself. Still, I believe that it is not ready for just about everything, not yet anyways. CRUD applications are so freaking easy to make with Rails as are so many other type of applications but I just don’t see it replacing any of the big guns for big projects, not yet anyway.

Most of the hype behind Rails is just people coming from languages such as Java and VB that hate the cumbersome nature of those languages’ syntax and the complexity to build even the most simple things. But I will take complex and stable/scalable with a bit longer development time over simple yet unstable/moody any day of the week.