The pragmatic approach to Rails adoption

In stark contrast to Panda, Dave Thomas presents the pragmatic approach to deciding between J2EE and Ruby on Rails.

Using the full might of a J2EE stack to write a small stand-alone application is using a sledgehammer to crack a nut. But I keep hearing the sound of nuts being pulverized as developers seem to think that using anything other than J2EE is somehow unprofessional.

At the same time, there are situations that call for the shock and awe that is J2EE.

It’s definitely a continuum. Rails doesn’t replace, well, anything. Things are never replaced, but increase and decrease in relevance. Rails has decreased the relevance of a lot of environments, including J2EE, for a growing niche of application types. But it hasn’t replaced them and never will.

With that out of the way, Dave moves to answer “when is Rails appropriate?” and “how can I introduce it where I work?”. Great advice for picking an entry and moving your company through the transition to Rails.

Oracle, Java Panda says LAMP doesn't scale

There was a time where I would have jumped in and attempted to educate a guy like Debu Panda. Now it’s more of a comical relief. Like when old people talk about how they’re never going to get a cell phone with an off sense of smug:

If you are looking to build a web application with LAMP then it may be simple to develop but it may have scalability issues and maintainability issues due to it’s inherent architecture.

Like, whatever, dude.

Matz manages Ruby team through Basecamp

Matz, the creator of Ruby, has signed up for a Basecamp account to help the committers team collaborate on the development of Ruby. What an honor.

Note, the intentions are not to use Basecamp as a ticketing system (it’s not well suited for that), but rather as tool to help the informal division of labor that’s already going on in private and on the committers mailing list.

Rails is reaching the tipping point

We’ve had a lot of discussions of Rails as a disruptive technology, but now David Geary is focusing on explaining the growth (and imminent growth) through the lens of Gladwell’s tipping point. Geary believes that Rails is standing right in front of the tipping point or perhaps even on it already:

In the end, of course, this blog entry is simply my musing. Will Rails hit a tipping point and become widely adopted in the near future? I am certain of it; in fact, I think the tipping has already begun. But, of course, only time will tell. In the meantime, I continue to have a blast every day trying out new things in Rails and figuring out the best way to show my future readers how to do them too.

Alonovo: Socially-responsible shopping on Rails

Alonovo launched a little while back. It’s a market place that provides a way to do “socially-responsible shopping”. That is, buying from companies that behaves according to how you think they should. So no sweat shopping and the likes. You set your values and are presented with offers that comes from compliant companies.

Oh, and it’s a Ruby on Rails production. Very nice.

Cartographer: Effortless Google Maps in Rails

Courtenay and bousquet are behind Cartographer that allows you to integrate Google Maps in your Ruby on Rails application with no effort. A few API tastes:

<%= gmap(:mapname=>"my_map", :width=>"50", :height=>"120") %>

<%= gmap(:width=>"500", :height=>"500", :type=>:satellite, :point=>[-122.14944, 37.441944]) %>

<%= gmap(:mapname=>"foo", :white_div=>{:background_color=>'black', :height=>'40'}) %>

Pretty nifty stuff! See also bousquet’s announcement.

Why Ryan Tomayko switched to Ruby on Rails

Ryan Tomayko is a long-term Python guy in search of a web-development platform for his small tech company. His evaluation first went along the lines of safety vs freedom languages where he rejected the previous .NET course and chose to focus on the LAMP stack. Not too surprising for a Python guy, but his next choice was:

I knew that Rails had the Basically Good, Basically Complete Web Framework with a Huge Community – Python will have one too. But I lost it when I found that Ruby has a standard build tool in Rake, a standard documentation tool that meets my needs in RDoc, and that Gems were everywhere. I had assumed that these would be no further developed than their analogs in the Python world.

The long and short of it is that my evaluation turned into what looks to be a long term relationship. I’m committed to my responsibilities on the Python projects I have going right now and I have a ton of existing applications and utilities written in Python that aren’t going anywhere but Rails ganked 80% of my future code somehow.

Back in the day when I came over from PHP, I had many of the same reservations regarding tools and libraries. That surely, Ruby would have less and worse than the reigning web champion. Surprise, surprise: I didn’t. And the rest is history.