Comments on: Is Ruby on Rails dead?

By: ungeheuer

ungeheuer — Wed, 07 Sep 2011 08:25:03 +0000

agree. rails is dead as can be.
but it really bugs me that those folks are doing
such a good job of pretending it isn’t.
what with all the conferences all over the world,
all those book publications, the frequent rails
releases with tons of new features, an ever growing,
very commited community..
not to mention all the successful startups using
rails.
if you didn’t know any better, you’d think rails was
actually a thriving framework.
but hey; we know better!

By: Rick O'Shay

Rick O'Shay — Fri, 02 Sep 2011 22:06:24 +0000

Yes. It’s dead, if crap can said to have been alive. Ruby on Rails was the object-oriented, test-driven replacement for the PHP crowd and its fallen by the wayside. The big selling feature was a short learning curve with enough power and flexibility to build a real website. The learning curve is of no value to the learned, nor to customers who use the learned to build their applications; it’s only valuable to developers in training, and the customers you hire them to create software.

By: dean

dean — Mon, 25 Jul 2011 20:39:45 +0000

I would say Rails is dead. The community was larger 7 years ago and is nearly non-existent now. There are about ten jobs using Ruby/Rails in the country. And Ruby has done several things to prove again and again that it is not production ready. Ever try upgrading a single build of Ruby? More often than not, it’s worse than going from ASP.Net 1.0 to 4.0 or PHP 3 to 5!

It was a cool experiment, and not a complete failure. It allows users to build websites extremely fast, but its future maintainability is worse than even bloated Java. Generally it was well designed but very, very poorly executed

By: developer

developer — Mon, 28 Mar 2011 17:42:26 +0000

Let the facts speak for themselves:

1. Twitter, RoR only claim to fame, dropped ror.
2. Zed, the writer of THE rails server, Mongrol, decided the ROR community is one of the shittiest communities around and basically told it to fuck off.
3. ROR is dead.

By: Rick O'Shay

Rick O'Shay — Wed, 24 Nov 2010 20:03:36 +0000

The slope of the learning curve is moot and of no consequence to the customer or the application, for those who live on the flat part near the top. RoR is a superior alternative to PHP, based on excellent principles, but it’s a tricycle with training wheels.

By: eric

eric — Fri, 22 Oct 2010 19:30:36 +0000

anyone that touches ruby would never go back to php as their preferred scripting language.
the unintelligent usually have a hard time with adapting to change.
if something comes along that is more enjoyable and productive than ruby, I will switch, but for now ruby is top.

By: M Kilroy

M Kilroy — Mon, 02 Aug 2010 16:16:49 +0000

I started as a front-end designer and have slowly become more interested in dev. Like many who took this path, I went via PHP and have never used .NET or Java.

I got tired of using php frameworks and tried Ruby/Rails. Being a recently-converted developer, I know I was late to the party but thought I at least better check it out and make my own decision. I’m definitely not in any rails ‘cult.’

But Ruby seems to be absolutely cleaner, more rational, and more useful than PHP, and to have more interesting projects in the community. I don’t want to write html and css now that I can write haml and sass.

At work, we have to use Zend, and it feels clunky in comparison.

My only gripe was that it was a bit of a mission to install Rails. All that command line stuff was uncomfortable.

I can see its appeal to startups, but also why it would be difficult to use in big corporate systems.

I’m glad I found the time to learn it (on weekends). I don’t share the opinion that “nobody has the time to sit down and learn something completely different in order to be a little more productive.” We all work hard, but I’ve seen many people superseded because they’ve failed to try different things, and it is really sad.

For the same reason I looked at RoR (curiosity about how things might be done differently), I studied Lisp with no intention of ever using it in the workplace, but found it gave me insights into functional programming I could use in javascript the next day. So it can even be useful to have a look at a 50-year old language, right?

I doubt RoR will die soon but don’t doubt there is less hype about it now.

If I was able to found a startup tomorrow, I would use it. I couldn’t afford to do otherwise.

Cheers

By: Johnny X

Johnny X — Mon, 19 Jul 2010 20:27:09 +0000

It’s now 2010, and yeah, it’s pretty much dead. A few clingers like that die-hard obie guy, but other than that you don’t hear that much about it anymore. It was supposed to replace Java, according to people like Bruce Tate, but obviously he was WAY wrong.

By: Diamond Glass

Diamond Glass — Thu, 15 Jul 2010 19:16:55 +0000

Rails isn’t just on its way out, it’s almost gone. Almost no one uses it anymore. It’s too much work for a less complex outcome.

By: Green Guru Landscaping

Green Guru Landscaping — Mon, 14 Jun 2010 17:26:34 +0000

I’m with Someone: ‘You say that “ISPs have never really been that enthusiastic about it”, and I fail to see why ISPs should care about any webdev framework.’ Your little article here really doesn’t make sense. It’s like you just copied and pasted technical words from a web developers’ handbook and threw them into paragraph form. This doesn’t even begin to make sense.