Item — HN Reader

I've shared my sentiment here before on why I'm not going to use Rails anymore. Imagine having your code working fine, and you update a MINOR version 3.2.x - and your ORM starts returning results that it didn't used to.

Heh.

Not worth the heartburn. I've switched to a saner, more tought out framework. Rails is gorgeous, but not safe to use for any serious systems where you're in a small team.

2 comments

What did you switch to?

Probably ASP.Net MVC -> https://news.ycombinator.com/item?id=5410169

ASP.Net MVC4.

If you're willing to trade off stability for features, the Rails 2.3 line still receives security patches to this day. You can upgrade to Rails 3 when Rails 4 comes out.

If you're willing to make a slightly different trade-off, just apply the security patches as they come out and don't upgrade minor versions without integration testing.

I have heard, but can't find an official reference to it now, that Rails 2.3 will stop receiving security updates once Rails 4 is released. (I suspect that patches will still become available for serious issues even once official support is dropped.)

Rails Core will not support 2.3.X, in any fashion, after 4.X is released. It is not relevant to their interests. It is very relevant to my interests, so watch for a coming announcement on my blog, or (an alternative) switch to Gthub's fork of 2.3.X.

Maintenance policy: https://groups.google.com/forum/m/?fromgroups#!topic/rubyonr...

Right - that's what I've heard, but that email doesn't explicitly say that.

Right, so you have your migration to Rails 3 ready to go as soon as Rails 4 ships. When Rails N has shipped, consider Rails N-1 to have become the "stable" release and Rails N-2 to be deprecated.