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...
Only that wall is at the end of a 50 mile runway. Don't let these sorts of pronouncements scare you ... by the time you get to this bogey man 'wall' you're going to be doing a million page views a day, dealing with replicated databases or just generally dealing with really big big problems. And even then you'll have a very supportive community of people who have had the same exact problem ... (example ... github coming up with Unicorn to help them server pages in a better way for them).
Long story short, for starting out and even a good ways into any application lifecycle. Rails is going to do you just fine.
However, this "magic" comes at a price, and at some point you will hit a wall, and if you're a very attentive programmer, you'll have been paying attention to what the magic has been accomplishing without you behind the scenes, and you'll be able to figure out a way around it without scrapping your code base. If you haven't done that, then you're going to pull your hair out in frustration.
To be honest, I'm not a huge fan of rails or other magic frameworks for anything other than prototyping, but ymmv, I definitely understand why people like it.