I don&#x27;t get the purpose of the article. So the first complaint is that programming was hip but isn&#x27;t now. Who cares? Do you program because it is hip or did you choose the language, framework and so on because it is hip? I hope not. Maybe if that is one of the concerns, just change the language. Is Nodejs still hip or Go or do you need to program your stack in Swift even before the language is really stable or as an official package manager?<p>The next complain is that Ruby is slow. Ok, fine maybe you build the next Uber and you need to scale almost unlimited. Then maybe Ruby is not the tool you should use (disclaimer: I know not that much about scalability with Ruby). Before you need to scale you usually need to get to the market and if your stack is easy and fast to build with Ruby just use Ruby and then rewrite critical stuff with &quot;faster&quot; languages. Hopefully everything is faster then and you don&#x27;t discover that the database is the bottleneck.<p>Only the last complaint is something I get, debugging and all the gems. That is something I had problems with when doing Nodejs projects too. Still, being able to add just a module that does all the OAuth2 handling and I just needed to add 2 or 3 lines of code was nice.<p>So in the end, what is the point of the article? Is it just the roadmap of Ruby that bothers you? Is it the Rails community that consists of lazy thinkers (not my opinion)? Or do you see all the people doing fancy and hip stuff like Protocol-based programming and functional programming and you doing still OOP stuff? If that&#x27;s it, learn a language from those realms and try it, I&#x27;m pretty sure you will find those being the silver bullet either.<p>I know my comment sounds like a rant, it is not meant like that. I&#x27;m just wondering what got you to write the article and what is really bothering you. Also, why are so many people afraid to miss the next big thing? While developing and working with a language and framework you&#x27;re not just learning that particular language and framework but you learn how to approach certain problems, what pitfalls to consider and so on. You can use that with most other language&#x2F;frameworks again. You didn&#x27;t waste your time.