Yesterday, a new micro-framework named Metal has been introduced which allows one to intercept requests, whether it be for performance reasons or simply to call out to another framework. Sinatra has already been demonstrated, Merb can’t be far behind.
I love it when a plan comes together
Also there’s all kinds of interesting development at the Rack level. or example Rack::Cache [link] which implements HTTP caching semantics in Rack so you can write you app to be cacheable from day one.
Indeed, it was rack-cache that finally made me ‘get’ why rack was interesting.
I think referring to metal as a micro framework is over stating it, we added it simply to allow people to ‘drop down to the metal’ for those rare cases where you need ‘super fast’ responses. Things like pollers or status urls.
We’ve completely rejigged our internals to be rack from top to bottom. Our session store is now handled by middleware, our dispatchers only speak rack, our integration tests use rack also.
Ok, that title is terrible... But as Sam mentioned , Rails has adopted Rack ! I’ve managed to avoid Ruby in favor of a superior language (which I type with my tongue firmly in my cheek), but when I did use Ruby and Rails, Rack was of definite...
Last week I finally caught up with the state of Ruby - the language, the community and the tools in fashion. I’m impressed. These guys seem to be doing a lot of things right. I’d taken a break from Ruby a few months ago, after Metaprogramming Ruby...