The entire process takes about 90 seconds

At any rate, what impresses me most is that the flaw was discovered, identififed, and patched in less than 2 days. Now THAT is the open-source community at it’s best. I’ve listened to pundits on both sides of the open-source question debate the hypothetical scenarios. I’ve heard those on the closed-source side chiding – “Open source software is inherently unreliable and insecure!” But don’t get me wrong. I’ve spent about 16 years in the industry and most of that time was spent on that very side of the argument. And I honestly believe I’ve earned the right to articulate an educated opinion on the subject. And no matter how you look you’re faced with one question: When was the last time you saw Microsoft turn something of this nature around in that time frame? And, if you’re honest with your answer you HAVE to give kudos to the OS community.

Keep it up guys!

If you haven’t already heard about it the Rails framework is a relatively new approach to “agile” web design. I won’t go into too many details in this post (I’ll save that for later) but the core of the framework is that it is “convention based” as opposed to “configuration based”. In a nutshell the architecture of the framework DRAMATICALLY reduces the web development production life cycle. Functionality that would typically take months to pull off with more conventional technologies (i.e. ASP.NET, PHP, PERL, etc.) can be completed in a matter of weeks – if not days by building on the Rails framework.

If that peaks your curiosity (or if you even have the faintest idea what I’m talking about) head on over to the Ruby on Rails site and see what it’s all about.

If you’re interested, the specs are below..