
ROR
Get flash to fully experience Pearltrees
Rails SQL injection vulnerability: hold your horses, here are the facts – Phusion Corporate BlogPhusion Corporate Blog
Update: see also the article Securing the Rails session secret . Update 2: a statement from Michael Koziarski of the Rails security team regarding the severity of this bug has been added. He urges people to upgrade immediately. Please scroll to the “Conclusion” section for details. Update 3: new advisories ( CVE-2013-0155 and CVE-2013-0156 ) have been published. These vulnerabilities are unrelated to the one reported in this blog post, but are extremely critical.I was quite surprised by how much feedback I received on the original post . You should read the first one before reading this. I'm writing this post to respond to some common questions, points, and concerns. Setting The Record Straight It seems the point of the previous post has been lost in the title.
Moving on from Rails: Part 2
ROR Tuts
Bundler: The best way to manage Ruby applications
Ruby Under a Microscope
Buy Now Learning Ruby Internals Through Experiment Have You Ever Wondered How Ruby Works Internally? Everyone knows that Ruby is a powerful language. Its dynamic nature allows you to concisely write the code you need to actually solve a problem instead of burying yourself under mountains of boilerplate.You may have heard last week how Innokenty Mihailov’s great Enumerable::Lazy feature was accepted into the Ruby 2.0 code base. But you may not have heard about an even more significant change that was merged into Ruby 2.0 in January: a new algorithm for garbage collection called “Bitmap Marking.” The developer behind this sophisticated and innovative change, Narihiro Nakamura , has been working on this since 2008 at least and also implemented the “Lazy Sweep” garbage collection algorithm already included in Ruby 1.9.3. The new Bitmap Marking GC algorithm promises to dramatically reduce overall memory consumption by all Ruby processes running on a web server!

