Re:The Costs of Keeping Your Rails App Up to Date, Or Not
by j45 on Monday January 27, 2014 @01:56PM
(#7132308)
Differentiating Rails as a framework and not a language is helpful when people compare framework to a language and say that language is inadequate. I'm not sure if that's why you're clarifying this?
Frameworks tend to extend languages to the web/internet, because none of them handle the web very well. I only know of a few languages specifically, and written for the web/internet first.
Re:The Costs of Keeping Your Rails App Up to Date, Or Not
by yxhuvud on Tuesday January 28, 2014 @09:52AM
(#7137335)
Not caring about being backwards compatible is perfectly fine choice.
Not caring about having reliable guides for updating between versions (which include keeping information around for upgrade between outdated versions. These needed be updated, but they should still be possible to find for people that use old versions) is less ok. The situation tend to be decent if one upgrades between current versions, but that information needs to be kept, which isn't the case today. It is fine not to update them, but they still must be possible to find.
Rails is a framework.
Also, Rails isn't trying very hard to be backwards compatible, either (which I never found to be a problem).