Browsing the linked GitHub code on the OP's link relating to the new secure_password stuff - does this make the authentication code used in the above tutorial obsolete - the commented example on GitHub indicated included BCrypt based password storage/authentication method ... ?
Any comparisons between Jammit and Sprocket will be welcome.
* jammit uses config/assets.yml, sprockets uses inline requires
* jammit loads individual files in development, sprockets concatenates
* sprockets compiles coffee with :bare => false by default. I don't know what barista's default is
Would love to see a workaround in sprockets (to make each js file included separately in dev mode), but until then I'd say Jammit is the way to go.
* Incompatible change: Rake DSL commands ('task', 'file', etc.) are
no longer private methods in Object. If you need to call 'task :xzy' inside
your class, include Rake::DSL into the class. The DSL is still available at
the top level scope (via the top level object which extends Rake::DSL).
I use Devise and Mongo Mapper. The Mongo Mapper for Devise gem depends on Devise 1.1.x, and this causes a bunch of deprecation warnings, but it works. I don't know if the latest Devise has this fixed, as I can't run it due to the Mongo Mapper for Devise dependency.
Some hand editing of development.rb to remove the debug_rjs setting and some editing to change my use of stylesheet_tag and my app ran ok
I'm not using the cool new asset pipeline yet, but my app runs with 1 hour of work.
I've upgraded Mongo Mapper to 0.9.1 to take advantage of it's Rails 3 integration, and it works with Devise 1.3.4 which removes the deprecation warnings.
To do this, I had to pull down the devise-mongo_mapper plugin to avoid version conflicts - it works with the newer code with no changes.
Mongo Mapper 0.9.x has a new configuration hookup that I had already written myself, so that code had to get a small change.
Joint, a Mongo Mapper plugin, doesn't work. I was going to replace Joint anyway for my own needs, now I need to do it today instead of next week.
Now I'm 2 hours in, and still not working on the Asset pipeline work I want to do, but my app is running except for the Joint bits
My next step is to fixup my morass of CSS and JS files to use the Asset pipeline correctly. That's probably another hour or so.
edit: Your printed technical book was essentially worthless the moment you bought it, given how fast most software evolves these days. But, I'm guessing you mean: 'will this make my book so outdated as to be worthless in terms of learning.'
The answer is still no. All of the major new features are, essentially, optional, with the exception of jQuery, but hopefully you were already using that anyway.
The Asset Pipeline, SCSS and CoffeeScript are major new features, but you'd likely need to read up on SCSS and CoffeeScript separately anyway. The Asset Pipeline can probably be understood with a couple good blog posts.
HTTP streaming: same thing. Also, it's—again—an optional feature.
I was thinking how long it took for "Agile Web Development with Rails 4th Edition" to come out and now 3.1 is on the way. Luckily guides like railstutorial.org update along with new Rails releases.
Saying that, Rails 3.0 to 3.1 isn't like 2.x to 3.0 (where your books WOULD have been useless). A lot of the changes are evolutionary, and there's nothing stopping you from learning on the latest 3.0.x branch with your book before tackling the (fairly straightforward) 3.0 to 3.1 upgrade process, once you've got your Rails knowledge bedded down.
That being said, I'm currently working on a Rails 3.1 version of the book. Stay tuned to http://news.railstutorial.org/ to get an announcement when it's ready.