> You say that like it's an epic conquest to learn Rails.
> [...] there's also plenty who have taken the weekend or so it takes to get a good working knowledge of Rails.
It is a fair enough conquest to learn Rails the proper way, knowing exactly what is happening under the hood.
Rails productivity doesn't come from how easy it is to generate some pre-built basic controllers or models without knowing what is involved, Rails productivity comes from how well it is engineered and connected in the whole picture. In fact, all Rails pro's will tell you that they have stopped using those "automagical features that make productivy fast" as soon as they were able to understand what they were doing, for the sake of more granular customization.
So, in 2 words, you won't have a good working knowledge of Rails in a week-end, expecially if you don't know ruby. You'll just learn to use some "generators".
> If a language or framework has major security holes, it should
> fail in the marketplace
It should in a perfect world designed by an IT professional which fortunately it isn't.
It will not in reality, and fortunately we have plenty of cases for this.
> I'm going to assume it's a troll post. After all, when I see your username I can't help but imagine [...]