I started to love Rails because of this and I still do. I get my bread and butter with Rails and I love my work because of it (and of course for the challenges). Four years and counting...
One of my biggest annoyances though is the really REALLY hard upgrades between different Rails versions. 2.x to 3.x was several days project including testing etc. 3.0 to 3.1 or 3.2 adds the nice assets pipeline, which of course might brake some javascript if you have lots of legacy there.
A minor change in ActiveRecord (and minor Rails upgrade) changed the behaviour to use SHOW INDEX instead of describe before loading data. The result was hazardous. So when you start to have lots of traffic, be very careful when upgrading Rails itself. And read the changelogs and the diffs.
I would honestly rather have this than the situation with python and django. While its awesome they're supporting python3 in 1.5 that took longer than I'm comfortable with.
What I've learned with rails is that the minor version you start a project with should stay the same for the sake of your sanity, until after project completion. Concerning yourself with incremental improvements should be avoided until you are between major versions of your own codebase.
One of my biggest annoyances though is the really REALLY hard upgrades between different Rails versions. 2.x to 3.x was several days project including testing etc. 3.0 to 3.1 or 3.2 adds the nice assets pipeline, which of course might brake some javascript if you have lots of legacy there.
A minor change in ActiveRecord (and minor Rails upgrade) changed the behaviour to use SHOW INDEX instead of describe before loading data. The result was hazardous. So when you start to have lots of traffic, be very careful when upgrading Rails itself. And read the changelogs and the diffs.