This is the 12th episode of This Week in Ruby, please consider subscribing to my feed so as to not miss any weekly installments. Also, if you enjoy the series and this blog in general, please consider recommending me on Working With Rails.
I’d like to start this edition by apologizing to my readers for the delay in publishing this edition. Things got pretty hectic last week.
As far as I know, there are no updates regarding Ruby’s vulnerabilities, but if you’re aware of any, feel free to state so in the comment section. Meanwhile, BreakingPoint Systems published a couple of extra problems that were discovered while analyzing those pesky security issues. You can read about them here.
As you may have inferred, I’m quite interested in the optimization of Ruby code. Ilya Grigorik wrote 6 nice tips for optimizing Ruby MRI, which may come handy to you.
A new chapter was added to The Book of Ruby by Huw Collingbourne. Read more about it and download it here.
The Ruby community is big on TDD and BDD and there is no doubt that testing is fundamental for good quality software. RailSpike opens a can of worms with its thought-provoking article, Testing is overrated. Whether you agree or not with its findings, it is definitely worth a read.
Sinatra is an ultralight Web framework, while Datamapper is considered by many to be a valid substitute for Active Record. Nick Plante shows us how to use them together to create a Pastie clone. If you are into Datamapper or would like to just get a feel for it, consider reading over this cheatsheet as well.
In conclusion, InfoQ published a Metaprogramming roundup and the second part of their RubyKaigi 2008 coverage. The most interesting bit is about the exciting prospective of standardizing Ruby. That would be a leap forward for the language and our community.
To keep the good times rolling, the third edition of This Week in Rails is available on the official Rails blog.
I sincerely welcome and appreciate your comments, whether in agreement or dissenting with my article. However, trolling will not be tolerated. Comments are automatically closed 15 days after the publication of each article.