As someone who missed the early Rails train, I'm not really seeing a lot to love anymore. It seems like Rails tried to do exactly what MSFT was doing with ASP.

As someone who missed the early Rails train, I'm not really seeing a lot to love anymore. It seems like Rails tried to do exactly what MSFT was doing with ASP.net - Give an excellent set of defaults you don't have to think about. The problem with that (and it's the same problem in Rails) is that "excellent defaults" change rapidly - much more rapidly than most production code-bases. So you end up with outdated defaults, and documentation fragments everywhere (this is actually FAR worse in Rails, because ruby hands you a million and a half ways to accomplish most tasks). The end result is a framework with a ton of baggage, poor documentation, and riddled with "That way is not proper anymore" style footguns. It's quick to knock stuff out with, but the second your team is bigger than 10 devs - Rails is a fucking ugly beast. Honestly - ASP.net was crap, and I prefer it to modern rails on large teams. --- So no - I personally don't see Ruby making a big comeback anytime soon, since its poster child - Rails - kinda sucks these days (and no disrespect to the authors, I think this problem is unavoidable in frameworks that give opinionated defaults - 1 set of opinionated defaults is awesome, 6 different sets of opinionated defaults that are no longer compatible is fugly, but if you don't update your opinionated defaults the framework rots anyways.) That said - I actually quite like Ruby as a scripting language. I just really wish it hadn't become so tightly bound to Rails. Just like I quite enjoy C# compared to java, but I still don't want to write ASP.net applications.