Yesterday the first preview for Ruby 2.1 was announced. The release notes gave a first idea of what's new, but didn't go too much into detail. To find out more, you are pretty much left with diving through the Ruby issue tracker. Since I was already aware of most of these changes, I thought I'd write a quick overview post.
Site note: Obviously Ruby 2.1 includes all the juicy Ruby 2.0 features that I'm not going to repeat in this post. Refinements
Refinements were added in Ruby
Both @bmizerany and @konstantinhaase will be at @magmarails next week. Get your ticket now: magmarails.eventbrite.com — Sinatra (@sinatra) October 5, 2011
In 2011 I was supposed to speak at MagmaRails.
At the time, I was working on Rubinius and related projects from Portland, Oregon. The whole thing was sponsored by Engine Yard. In case you didn't know, they rock.
Anyhow, they would have covered my trip to Manzanillo. Would have. But then Hurricane Jova decided to can
I'm about to release Sinatra 1.4.0.
A few house-keeping jobs are still outstanding, like bringing the website up to speed and running it on a few more apps in production (though we've been running it in production for Travis CI for quite a while without issues) and then we're good to go.
If you want to give it a try right now, you can install the prerelease via gem install sinatra --pre. For more infos, check out The Bleeding Edge from the official Sinatra documentation.
A while back I implemented a functional Sinatra clone in six lines of Ruby code.
I recently gave a talk about this and other useless but amusing things at a conference in Melbourne and they've just released the video:
And here are the slides:
I hope you enjoy it as much as I did!
As the core of my Ruby Summer Of Code project, I have partly rewritten ActiveSupport::Dependencies. I will give an introduction to common reloading strategies and their implementation and discuss my changes to Dependencies. Even though this part of ActiveSupport is hidden away and not well known, all Rails developers rely on its proper functioning, as it is responsible for autoloading and reloading Ruby code. It is also responsible for producing error messages like "A copy of Something h
This is an excerpt from my bachelor thesis. Core principles
Seaside's approach to web development differs from most other web frameworks, such as Django or Ruby On Rails, by explicitly breaking with common patterns and principals the web is built upon, such as being stateless, having meaningful, maybe even restful URLs or using template systems.
When doing web development you often have to work with the construct of a session, that allows one to keep state in between requests