Mr. Frenandez’s post on Rails Maturity has sparked quite a reaction, most notably from Mr. Bowkett. There was one part that made me happy and frustrated all in one go:

Actually, I hate to end on a bad note, but I really think that there’s some urgency to all this and that our collective failure to set high standards for the community is strangling the continued growth of Ruby and Rails overall.

Tom Mornini: Our customers at Engine Yard are screaming for more developer capacity, and in fact, TWO previous customers abandoned Rails (one for PHP and the other for Java) simply because they could not find enough skilled and savvy Rails developers to move their projects forward.

It’s not a problem only for Tom and Engine Yard. At Hashrocket we’ve been helping organizations transition from legacy technologies to Rails and they all have difficulties finding qualified developers. I know that folks like Courtenay at ENTP are having the same problem. Please don’t shoot the messenger. Something has to be done about this, and I think it’s more important than Rails 3 or anything else we are currently excited about.

If this is you, if you’re looking for someone who would make a great rails dev, please post in the comments.

[update] I would also love to work with erlang, if anyone is listening.

After working away at it for a month or two of scraped together free time, whilst learning erlang, grove is done and there’s a screencast to demo it.

(By done I mean done for now, I’ve got some other projects to attend to for a bit)

http://nickelcode.com/grove

http://railslab.newrelic.com/scaling-rails

Been watching these, and they are great from every perspective. Even if you’re rails app is small and doesn’t really need to scale, the client side optimization tips in the first video are awesome stuff to put into practice.