You'll probably be happier with your life if you let go of that, because this cycle has been part of software as long as I've been involved with it, and I expec

You'll probably be happier with your life if you let go of that, because this cycle has been part of software as long as I've been involved with it, and I expect that it will always be so. For any given technology which manages to take off at all, there's generally at least a ten year span during which some groups of early adopters are calling it "old and busted" and moving on, while other people are just discovering the "new hotness" and piling in. Just because this guy has switched from one group to the other doesn't mean you need to follow him; if the technology is good and meets your needs then hey, take it on, it'll be great. The other thing that happens is... well, most of what this article is talking about has nothing to do with technology in the first place; it's more about the community built around that technology, and the fact that the author no longer feels like that community is going in a direction compatible with his needs. I'm not part of the ruby community at all so maybe he's right and the "roadmap for rails is bleak" - but I'd bet that it's really more that it has developed further but not in a way that suits this author's needs, so he feels disappointed and alienated from the community, and he is observing that he and the rails community are drifting apart and will soon get divorced. This says nothing whatsoever about the compatibility of the current rails community's direction with your direction, and it makes no useful predictions about the future development of the rails technology and its potential compatibility with your needs. It could be that the same forces driving this author away from rails are the ones which have brought it to your attention as something worth learning about and investing in.