Ruby on Rails rides into Asterisk on RAGI

Asterisk is the open-source PBX that makes the phone an interesting and hackable device again. But the UI is more than a little geeky, which is where RAGI comes in. It’s the Ruby Asterisk Gateway Interface that serves as a bridge between Ruby on Rails and Asterix. Their pitch goes:

RAGI eases the development of interactive automated telephony applications such as IVR, call routing, automated call center, and extended IP-PBX functionality by leveraging the productivity of the Ruby on Rails framework. RAGI simplifies the process of creating rich telephony and web apps with a single common web application framework, object model and database backend. RAGI is available under the BSD license.

Pretty exciting stuff.

Need help testing Sybase and Firebird adapters

We have two new pending database adapters that could use some solid testing by people who have access to those engines. The first is a Sybase adapter by Will Sobel and the second is a Firebird adapter by Ken Kunz.

Please give both of them a spin and add any comments on their tickets. Also, be sure to note if either of the adapters should do something that doesn’t match the idiosyncratic approach in either of those engines.

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.