3 ms·

I've migrated a few large apps to 1.9/3.x, and it's the least fun I've ever had as a developer. The API changes in Rails and the burden they place on developer

I've migrated a few large apps to 1.9/3.x, and it's the least fun I've ever had as a developer. The API changes in Rails and the burden they place on developers makes me think twice before using Rails for new projects. After a while I ended up with a set of Vim macros that handle a lot of the superficial changes, but it's still painful drudgery that makes me wish I was working with a language and framework that's less fickle. And, be wary of projects with a lot of dependencies and plugins. Think very carefully before adding a single gem to a project.

pilif 14y ago
> The API changes in Rails and the burden they place on developers makes me think twice before using Rails for new projects you can always switch to PHP - they keep their API stable for years. Of course everybody equally hates them for that because keeping a stable API also means keeping warts. So what is the correct way to go? Only fix the API's I'm not using? That would be great for myself, but what about everybody else? I very much agree with your comment about dependencies though. When you decide to take on a dependency, never decide based on what work it saves you right now - also think about how much work it will be to fix it for the future. On the other hand, NIH is bad either. It's really hard to find the correct middle-ground.