We’ve been working with and on Rails for the past four and half years here at 37signals. The sum of those efforts just got a new label today: Rails 2.0.
It contains a ton of good stuff. Lots of things regarding our love of all things HTTP. The RESTful angle. Multiviews. Security improvements. Lots of speed tweaks.
It’s been a joy extracting all these features from their origins in Highrise, Basecamp, and the rest of our applications. Deriving frameworks from production code really is a pleasant way of arriving at something useful.
Nate B
on 07 Dec 07Congrats on a great release. I grabbed it this morning and have a new application up and running 6 hours later. The magic of Rails.
matt
on 07 Dec 07Waa. No bind variables in AR yet.
Although kudos on including the debugger.
Dmitry
on 07 Dec 07Great stuff! Thanks for all the hard work you’ve put into this.
Andrew Kasper
on 07 Dec 07In my book, you guys just got upgraded from “extremely rad” to “rad to the max.” Well done.
Jeremy Ricketts
on 08 Dec 07whoa
curmorpheus
on 08 Dec 07Great Job!
Jeff Carlson
on 08 Dec 07Woo-hoo! Congratulations. We love what you do to help the community and help people love their work again.
Chin
on 08 Dec 07Love every bit of it (as I have for the past couple of years), but still, calling 2.0 an extraction of basecamp/highrise code seems like a stretch. Pre 1.0 and 1.0, sure, no doubt – but from there on? What do the other members of the Core team think about it?
Sam
on 08 Dec 07Hey david,
Wouldn’t …
— # /avatars/45 => AvatarsController#show map.resources :avatars /people/5/avatar => AvatarsController#show map.resources :people, :has_one => :avatarbe quite limiting in terms of rendering different views, considering they are nested resources?
Also, how do you feel about having per Mime::type directors in views instead of multiple views in one directory ie. posts/ html/show.erb //without show..erb xml/show.erb //without show..erb ...
meh, just a few things that came to mind as i was reading the blog post.
PS: using it and loving it :)
Later
Sam
on 08 Dec 07awww shucks, my post formatting got fucked up! sorry!
James
on 08 Dec 07Congrats guys, and thanks — looking forward to using the new Rails. Will this version be released through Apple’s automatic updates for Leopard users?
Gordon Brander
on 08 Dec 07Congratulations! I’m really looking forward to using this.
Gordon Brander
on 08 Dec 07Good question James. I’d love to know too David.
eh?
on 08 Dec 07Its a gem. in osx
sudo gem install rails -y
worked for me…
Jake
on 08 Dec 07Any details on a new book?
Justin
on 10 Dec 07Jake: As far as I know, this is the first book to cover rails 2.0: http://pragprog.com/titles/fr_arr
Though I’m sure you were asking (and I’m curious as well) about a new edition of the Agile book…
Mohan
on 10 Dec 07Congratulations! David. Excellent Work. I’m really looking forward to using this.
Garth
on 10 Dec 07Best quote I’ve heard in a while. In the past, we’ve suffered from frameworks which have been born through design by committee. Rails is a refreshing change from this method.
BC User
on 10 Dec 07Basecamp is having performance issues today. Is this a result of Rails2.0?
JF
on 10 Dec 07The performance issues are related to some database issues which we’re working on. They have nothing to do with Rails. We’ve posted an explanation in the Basecamp forums.
AkitaOnRails
on 10 Dec 07Congratulations! Rails 2.0 is awesome!
I invite everybody to take a look at a screencast I’ve compiled yesterday. This is the classic Blog app built using Rails 2.0. I think it is the First Rails 2.0 full featured screencast around.
See it here
Kenn Wilson
on 11 Dec 07Justin: I have it from Dave Thomas that a new edition of the Agile book is not currently in the works.
Arik
on 12 Dec 07Thank you for Rails 2. Couldn’t have asked for any better of an upgrade. Keep it up guys, this thing is turning out to be standard in web development. Woo!
This discussion is closed.