After Rails' memory usage, I would say that the "magic" is the worst part of Rails. Wish I could have Rails, except a bit more explicit.
That said, with pry, it's pretty easy to dig down into the "magic" and see wtf's going wrong when something is borked.
Despite that minor grumbling, I'd say that Rails is still darn good! It's very mature framework (or perhaps more accurately, collection of frameworks) at this point. You can get stuff done quickly.
Most things really don't need to be SPA, and many (most?) don't need to serve up more than a few hundred or a few thousand responses per core per second.
That said, with pry, it's pretty easy to dig down into the "magic" and see wtf's going wrong when something is borked.
Despite that minor grumbling, I'd say that Rails is still darn good! It's very mature framework (or perhaps more accurately, collection of frameworks) at this point. You can get stuff done quickly.
Most things really don't need to be SPA, and many (most?) don't need to serve up more than a few hundred or a few thousand responses per core per second.