This post originated from an RSS feed registered with Ruby Buzz
by Obie Fernandez.
Original Post: Ringing Hell's Bells for Java
Feed Title: Obie On Rails (Has It Been 9 Years Already?)
Feed URL: http://jroller.com/obie/feed/entries/rss
Feed Description: Obie Fernandez talks about life as a technologist, mostly as ramblings about software development and consulting. Nowadays it's pretty much all about Ruby and Ruby on Rails.
David says, "Java has lost its aura of invincibility. It's no longer blasphemy to suggest that neither Java, J2EE, and the rebel frameworks are too complex for their own good. That it's both a fundamental, deep, and cultural problem where the solution is unlikely to come from within." via Loud Thinking
Near the bottom of his entry, David mentions my employer, ThoughtWorks, as working on commercial Ruby projects and looking for more. That is indeed true. ThoughtWorks has several ongoing Rails projects and we're figuring out how Ruby work aligns with our core offerings, traditionally directed at Fortune 500 enterprise-class projects. One of the commenters asked if any Rails work is being done at Fortune 500 companies. Well, the most promising approach to launching Rails projects (IMO) is to take on web-based application work with "quick time-to-market" requirements. Meaning, get it done and rolled out within the month or funding dries up and the stakeholders pull the plug. All big corporations have those projects happen on a regular basis. In fact, that's exactly what I've been doing for the last few months at one of the largest agricultural and construction equipment manufacturers in the world. It's just a matter of time until internal Rails success stories bubble up to the CxO level and start making appearances in the trade press -- wider mindshare that will continue to push Ruby and Rails over the tipping point.