When it comes to Ruby, I’ve recently mostly been blogging about Nitro, which I think will be a really great framework for writing web applications once it matures a little more. For the next version (0.25.0) the developers plan to concentrate on bug fixing, code cleanup and refactoring, as well as documentation. The current development version – which following my suggestion is now called Glycerin – can be fetched from a Darcs repository, so there shouldn’t be anything stopping you from valuable contributions! ;)
Ok, after my usual Nitro evangelism, it’s time to finally talk about the other excellent web framework Ruby has to offer: Ruby on Rails. I haven’t used it for quite some time now, but when I got bored a few days ago, I decided to once again start playing around with it. I’ve done some googling and found some nice articles, so here’s my suggested reading list for the aspiring Rails programmer (please note that this list doesn’t include docs from the official site, because they’re easy enough to find):
1. MVC: The Most Vexing Conundrum: Befrore you do anything with Rails, head over to Amy Hoy’s blog, and read her explanation of MVC, the design pattern Rails is following. I think it’s really important to wrap your head around the underlying principles of a framework before you start to use it, so make sure you really understand what Amy’s trying to tell you.
2. Rolling with Ruby on Rails: Once you got the basic principles, it’s time to visit ONLamp to read Curt Hibbs nice introductory article. It doesn’t really go into much detail, but I’m sure it will wet your appetite…
3. Really Getting Started in Rails: Now that you’re rolling with Rails, it’s time to go back to Amy’s site. There you’ll find this nice article that is meant as an addition to the previously mentioned “Rolling with Ruby on Rails”, explaining some of the whys and hows Curt had to leave out to keep his text short and to the point.
4. Rolling with Ruby on Rails, Part 2: Do you start to see a pattern here? Correct, it’s Curt’s turn again. In the second part of his introductory Rails article, he finishes off the cookbook application from the first part, before giving pointers to some of the more interesting features of Rails, like caching, transactions, testing, generators and so on.
5. Four Days on Rails: Now that you should have a basic understanding of how Rails works, you should definitely check out this excellent HOWTO by John McCreesh: “It’s about 40 pages formatted for double-sided printing on A4, and by the time you’ve read it, you should have a useful toolbox of Rails techniques and a good idea of where to look on the web for more information”.
If you take your time to carefully read this stuff, you should be pretty much up to speed in Rails development in less than a week! Don’t be passive while reading the articles, but start writing you own little app and constantly improve it while you learn. Once you feel comfortable with the basic principles, you can read some of the more advanced stuff, like Ajax on Rails, REST on Rails, Ajaxariffic Autocomplete with Scriptaculous or the Rails articles why the lucky stuff publishes on RedHanded. Have fun!