You are wrong about the frameworks not being as powerful as Oracle etc, but I don't blame you since it takes a long time to become familar with a large framework. I would also not have time to learn eg. any big Java framework, so I'm in the same boat.
I'm not trying to be a jerk, but I'm not sure you have a basis for comparison. "Oracle" is not a Java framework, it's just the company that acquired the Java trademarks from Sun. I guess they own the trademark for JEE too... but that's not really a "framework", and its direction isn't so much identified with Oracle. Java web frameworks would include things like Spring (used by most shops these days), Seam, Struts, Wicket, etc.
Anyway, I have written apps in "dynamic language" frameworks... including Rails, Django (sorta), Symfony, CakePHP, and node.js. It's just not the same. It's like comparing a car to a space shuttle.
That said, I don't mean that these frameworks are inherently "inferior" to Java frameworks. I'm just saying that they are different tools for different jobs. If you're building a site that isn't heavily dynamic on in the back-end yet needs to integrate easily with front-end AJAX, and you don't want to recruit and pay more for developers with experience in commerce or large enterprise systems... then it might be silly to insist on a full Spring stack. At the same time, if you're a large institution, writing an app through which business will be conducted or money changing hands... then you probably don't want a dynamic language framework, because the framework and its developer talent pool are not as accustomed to dealing with the challenges that your project will face.
When we're used to swinging a hammer, everything starts to look like a nail... but the reality is that there is plenty of room for both a hammer and a screwdriver in the toolbox.