How to Marshal Procs Using Rubinius
The primary reason I enjoy working with Rubinius is that it exposes, to Ruby, much of the internal machinery that controls the runtime semantics of the language. Further, it exposes that machinery primarily in order to enable user-facing semantics that are typically implemented in the host language (C for MRI, C and C++ for MacRuby,...
What’s Up With All These Changes in Rails?
Yesterday, there was a blog post entitled “What the Hell is Happening to Rails” that stayed at the number one spot on Hacker News for quite a while. The post and many (but not most) the comments on the post reflect deep-seated concern about the recent direction of Rails. Others have addressed the core question...
The Rubinius Team Wants to Bribe You (With Stickers and T-Shirts)
You've given Rubinius a spin, right? And contributed code to the project? If you didn't already know, Rubinius is an 'alternative' Ruby-sorta-written-in-Ruby implementation that's production ready and has been going from strength to strength recently (I post about...
Getting Comfortable With Rubinius’ Pure-Ruby Internals
You probably know that Rubinius is a Ruby whose implementation is mostly written in Ruby. While that sounds nice in theory, you may not know what that means in practice. Over the past several years, I’ve contributed on and off to Rubinius, and feel that as Rubinius has matured since the 1.0 release, a lot...
May 17: The Happy Streets of Wilmette
Book Status The Cucumber chapter is nearing final edit for beta. I cleared up a handful of errata, of which probably the most serious was a mistake on how to get the fixture data to pass the first test in the book. I’m hoping to get Beta 3 out later this week, and then I...
