Imagine all the syntactical delights of Ruby and Haml for your JavaScript. You write in a nice language, but get normal JavaScript at runtime. All whilst having full access to 3rd-party JavaScript libraries (jQuery, PrototypeJS), debugging support (it becomes pure, readable JavaScript), existing support from test suites (it’s normal JavaScript) and growing support from various text editors (TextMate, Vim, Emacs).

If we want mobile applications to stay around as a sustainable business, we need to be more honest about the strengths and weaknesses of a touchscreen UI, rather than salivating about an imaginary realm of unnamed possibilities.

Though we ended up switching to what I consider to be a technically superior product based on simplicity, we arrived there because of poor community interaction on the part of the Bundler developers.

Unfortunately vanilla Ruby modules lack support for many idioms popular in modern Ruby. Most importantly, we have become accustomed to composing our classes with meta-programming macros such as has_many, validates_presence_of or after_save. And modules weren't built with macros in mind.

I love Cucumber, but I hate writing step definitions. They are ugly, awkward to write and very, very boring: Most step defintions merely create objects for a scenario to chew on.

Pretty print your Ruby objects with style -- in full color and with proper indentation

Steak is like Cucumber but in plain Ruby.

When I realized what had gone wrong, the light almost blinded me.

Rack middleware for rate-limiting incoming HTTP requests.

Here you will find pointers to manuals, tutorials and references that will come in handy when you feel like coding in Ruby.

But then there are those posts where the author pastes 10 pages of confused code with no context whatsoever and then demands to know why they're getting funny errors. I find this sort of behaviour offensive to all the people who are basically dealing out free support. I'd rather spend my time helping people who actually give a damn.

ShamRack mounts a Rack app locally, just for your tests. It goes one further: it “mounts” it using Net::HTTP such that requests to the Rack app never hit any network.

As far as I know, the only plugin out there that handles this (semantic issue) correctly is Makandra’s Aegis. And they are GERMAN. It functionally works about the same as well. So props to them for that.

Asset Fingerprint Plugin for Ruby on Rails - allows you to use md5 or timestamps in query string or in asset filenames as suggested by Google Page Speed

Good stuff.

Where there was once a consistent API to manipulate and hook into the lifecycle of a persistent object, plugins must now perform very careful checks whether an object supports more advanced traits like transactions, observers or dirty attribute tracking.

The FUSE project allows you to create filesystems in userspace - which means you can create a filesystem without having to get your hands dirty and modify your kernel source. This is insanely cool, and can be used for many purposes. Here we're going to look at using the Ruby bindings to create a simple filesystem.

Here is a set of additive color model conversion algorithms that I found published on Wikipedia and have implemented in JavaScript.

Dokan Ruby is a Ruby extension library to write a file system for Windows. This extension also has compatible API with FuseFS (Ruby extension for FUSE). You can write a file system only in 25 lines.

We're excited to announce PDFKit, an open source library that makes working with wkhtmltopdf a snap.