In the context of technologies hitting a peak, and then experiencing a trough of disillusionment as people discover it won’t really solve the world’s problems in 10 year lessons, Obie asks (read through for more)

Perhaps we can skip the trough altogether? Has that already happened? What do you think?

I responded in comments, and reproduce my comment here:

No. Rails will not skip the trough. Just like everything else, as it ascends the hype-scale, people will jump on the bandwagon, and proceed to build slow performing, horribly modelled, insecure bug-ridden crap. And when their work fails to impress, they will, of course, blame Rails. They will say “Rails doesn’t have an effective IDE.” and “Rails doesn’t integrate with existing legacy database schemas”, and “Rails scaffolding isn’t secure.” and “Rails has a crappy debugger” and “Rails doesn’t have thread support”, and “Rails doesn’t have support for legacy security and management infrastructure.”

And so on, and so forth. In other words, all the objections that “Enterprise Architects” gave as to why they won’t use Rails, will be used as excuses for the people who decided to use Rails without actually checking to see if it made sense for their project.

Yes, even the mighty SOA must endure the Gartner Trough. (Hat Tip: Sam Gentile)