Exactly. A framework like Scorched forces you to find your own solutions to the problems you face, as opposed to being dependant on the solutions already established by others. A framework like Rails makes it quick to get an application up and running, because it provides solutions to a lot of those common problems for you. This is what lulls so many people into it. The problem is however, the time you save in that early phase of a project is often lost as the project develops further and matures. Pretty soon you begin to run into limitations imposed by those pre-made solutions, and this is where you're forced to delve into the land of magic, learning how it works, so you can make the amendments you need to make.
The problem with spending time in the land of magic, is that you're investing time and energy into learning something very domain-specific, i.e. you're spending time learning how to master problems specific to Rails and certain Rails components - knowledge that is unlikely to be very useful outside the scope of that Rails domain. When on the other hand you're forced to find your own solutions, the time you invest goes into knowledge and experience that will likely prove to be useful in a wider range of contexts, regardless of whether that solution is merely finding a library and applying it, or coding something from scratch.
That's kind of how I look at it anyway, plus, as much as I strive for that end product, being creative is what I enjoy most about programming and application development. I'm not suggesting Rails doesn't allow you to be creative, but the lower-level the framework or the less that is solved for you, the more opportunity there is for creativity.