[texel]

I've heard these references to "hitting a wall" a few times now, and it's a bit perplexing. From what I gather, it means that you'll get to a point where you need to understand more about the underlying framework in order to accomplish a particular task. Isn't this a given in any environment? Perhaps in some other stacks, you need to get your hands way dirtier way earlier, so the learning curve is much more spread out. But I don't think I've ever run into an issue with Rails where I've thought "oh no, the framework can't do this... time to start over." It's just Ruby, the entire thing is well documented, and there's a very helpful community glad to answer just about any any question you might have (in my experience, anyway).

That isn't to say that Rails is a panacea, or even appropriate for projects of every shape and size. But if you're building an MVC web app, then it's really well thought out, allows you to be very productive, and in my dealings with it, those benefits don't go away, even as your application grows significantly in scope and complexity. YMMV etc etc...