4 ms·
Are there anyone that can chime in on the current long-time support story for rails? How much commitment could one expect from the Rails community towards long
by e12e 11y ago
Are there anyone that can chime in on the current long-time support story for rails? How much commitment could one expect from the Rails community towards long time software life-cycle? To clarify, if I want to implement a solution (say a web/service portal) now, that I have a reasonable dev budget for, and a commitment to maintain with security updates (and bug fixes) for, say the next 10 years -- is rails 5 likely to be a viable solution?
I always had the impression (possibly false) that the Rails community was very focused on rapid development, but that it had a tendency to leave dead projects on the road-side to fend for themselves -- and that maintaining a project that was a few years old sort of implied massive forward-porting if you wanted to have a semblance of security updates?
Is my impression way off? Is there a "safe path" if one sticks with the Rails core?
- brianwawok 11y agoCurious to this as well. Django had a pretty public and reasonable long term support policy. However 10 year is a bit much. What did anything look like 10 years ago? I could see 3 or 4 year cycle though.
- e12e 11y agoAccording to wikipedia, Hacker News Launched February 19, 2007; 9 years ago. [ed: Other things off the top of my head, AFAIK both from the 90s: slashdot.org, webhostingtalk.com, twitter is from 2006 (obviously twitter and slashdot have been pretty much rewritten, not sure about wht.]
- brianwawok 11y agoRewritten is not the same thing as having to upgrade a library. Even most enterprise apps upgrade the big libraries within 4 or 5 years due to the CVEs that pile up (see struts 1)
- heartbreak 11y agoAt RailsConf this week Jeremy Daer specifically mentioned that Basecamp (formerly 37signals) was maintaining projects deliberately on older versions of Rails.
- tjbiddle 11y agoRails has really stepped up their game after Rails 3; really nailing down the API and conventions. Upgrades are much easier now (Moved from Rails 4.2 to Rails 5 in an short afternoon). Just definitely keep up with the minor releases; but the major releases will stay in good standing for a while too! Lock down all your gem versions and only update as needed; so if they ever break on a move to the next major version - you can act accordingly.
- gurkendoktor 11y agoWith any luck, Rails LTS will maintain a fork of Rails 5 when the time comes: https://railslts.com https://railslts.com