The Ruby on Rails 3 Tutorial screencasts are out
railstutorial.org
railstutorial.org
hnscreencasts
Be sure to apply the code on the checkout page to get the discount. The code expires at the end of the month.As always, the HTML version of the book is available for free at http://railstutorial.org/book. Now that both Rails 3 and RSpec 2 are in their final releases, I'm also gearing up for the planned Creative Commons licensing to encourage translation of the book. I already have volunteer translators for half a dozen languages; email me at the address in my HN profile if you'd like to be part of the translation effort.
As someone who has read your book (I actually did the first 8 chapters of the 2.3 version and then went back and did the whole thing for Rails 3--it's fantastic, by the way) I'm wondering how much additional value these screencasts really bring to the table (at least, from your perspective). I can definitely see it for someone about to go through the book for the first time, but it feels like there would be a ton of repetition for someone who has already been through it.
I'm curious to hear your thoughts.
http://railstutorial.org/samples?file=rails_tutorial_lesson_...
If you find yourself learning something new compared to just reading Chapter 8, then you can be confident that (for you) the screencasts will add value over the book alone.
Otherwise, thanks for creating this! I've really enjoyed the book.
By the way, this is why I always keep an eagle eye on the Hacker News comments on Launch Day. You guys rock!
On a related question, is Rails 3 a good idea for any new projects (especially those using ActiveMerchant) .. or should one stick to Rails2 until all the plugins/gems are ported ?
In which case, this tutorial is not exactly relevant (for me) right now.
I recommend PeepCode (and Railscasts) as a follow-on to the Rails Tutorial. In fact, last year at GoGaRuCo I pitched the Rails Tutorial project to PeepCode founder Geoffrey Grosenbach as "From zero to PeepCode."
The railstutorial screencast reminds me of railscasts - almost 100% editor/terminal/browser. Very hands on, very code-intensive.
Peepcode has a lot of organized section transitions, slides, visual aids, etc. The summaries and concepts slides are exceptionally useful. Also, Jeffrey talks about half as fast as Michael in railstutorial.
Both are great and I'm talking myself into buying the railscast package right now. I wish I hadn't already spent ~$100 on educational stuff already this month :)
I've been working through the HTML version; great job! I especially appreciate the coverage of Ruby Version Manager, git (topic branches, merging), Heroku deployment via git, and TDD via rspec. You can read all about something, but it doesn't really sink in until you've typed the commands yourself -- even if those commands are dictated word-for-word by a tutorial. I generally dislike video tutorials, but will take a look at yours.
I notice you used a 4:3 aspect ratio (960x720) and was wondering why not 16:9. There are screencast benefits to both so I'm curious.
I'm not entirely sure that "More is good" in this context. But then, I know Rails already so I'm not part of your target market, I suppose.
Still, I would feel somewhat daunted by 15 hours of tutorials and 1000 pages of documentation. Sounds more like .NET than Rails.
The bottom line is that there's a world of difference between a tiny toy app and a real-world production app. The Rails Tutorial screencasts do teach you a toy app along the way (Lesson 2), but preparing you to make industrial-strength webapps is their raison d'être (Lessons 3–12). As it turns out, that takes more than 15 minutes. :-)
P.S. The "1000 pages" number included the page count of the Rails 2.3 Tutorial book, which many people won't need (though it's still useful for people with legacy apps). The Rails 3 Tutorial book itself is only about 500 pages, and I've change the wording on the site to make it sound less intimidating. Thanks!
The famous 'build a blog in 15 minutes' was Rails' elevator pitch: intriguing, representative, but by no means a complete picture. You still needed a full reference to get real work done. That's what this is.
Also, as I mentioned, I'm not part of the target market, so my criticism may be off-base.