[apeacox]

After 18 years of programming in a wide range of languages (almost 10 spent on Ruby/Rails) I surely agree that Ruby is a joy to use for many tasks. A different opinion goes to Rails: it's speed of development is inversely proportionate to the time taken to reach a messy codebase if you follow the infamous rails way. You need some decent design pattern to get something that is still usable after 6-12months of active development. Performances and speed can be important for many aspects, especially when there are alternatives that offer same speed of development consuming 10% of the resources needed by a ruby/rails app. Can you put a non trivial web app written in rails on a 512mb ram/1 core VPS for production (serving responses in microseconds, and consuming only a total of 50-60mb of ram)? That's what I did with 2 apps written in Elixir/Phoenix. The speed of development was the same (if not better!) than Ruby/Rails, the apps are running on cheap instances and can be scaled if needed. The hate toward rails: it's getting more crappy on each release. Several new additions (especially in the v5.x) are pretty wrong (eg: global shared variables). Yes, it's still a choice, but it has lost the real game-changing that was few years ago.