3 ms·

A 2.0 release seems like a big deal; is there a rails practitioner around who could describe the magnitude of these changes to those of us who don't use rails?

by icey 19y ago

carpal 19y ago
I've been developing off of the preview releases for a few weeks, and there's nothing earth shattering. Generally, it just makes things nicer. I don't do a lot of AJAXy stuff, and I don't talk very frequently to clients that aren't standard browswers. If I did, I think I would have a lot more to gain from this release.
- michaelneale 19y ago
  That is probably a good thing. Rails is a great fit for what it does, a 2.0 danger was to do beyond its strengths. It seems to have evolved nicely. I look forward to using it. As for the questions about the lack of "scalability" improvements, I don't really care. Its not needed for what I use it for anyway (and probably the same for most people).
jraines 19y ago
One new thing is the ActiveREST module, which provides a lot of neat support for creating RESTful services. Between this and Ruby 1.9 there's some fun new stuff for RoR folks to play with.
qaexl 19y ago
The change between 1.1 and 1.2 was much more disruptive than the change between 1.2 and 2.0. The biggest changes are in reworking the RESTful controllers and cutting down the cruft. 2.0 is more polished and shinier now. The 2.0 release may be coming in close with the upcoming Ruby 2.0 release, which will be highly disruptive (YARV bytecode backend), though I'm not sure if Rails 2.0 will work fine without any changes in Ruby 2.0. Besides, I'm not really sure when Ruby 2.0 is coming out.
- russ 19y ago
  I've been hearing that by Xmas for Ruby2 and the Rails guys have been doing quite a bit of work to make sure Rails2 is compatible with the upcoming Ruby release. I'm not sure how much will need to change, but they have indeed been working towards making it compatible.
palish 19y ago
Keep in mind that as a tool approaches "optimal", it needs to be changed less and less. So if Rails' new features don't justify the jump to "2.0", its stability and user-adoption may.

A 2.0 release seems like a big deal; is there a rails practitioner around who could describe the magnitude of these changes to those of us who don't use rails?

by icey 19y ago

A 2.0 release seems like a big deal; is there a rails practitioner around who could describe the magnitude of these changes to those of us who don't use rails?

carpal 19y ago

I've been developing off of the preview releases for a few weeks, and there's nothing earth shattering. Generally, it just makes things nicer. I don't do a lot of AJAXy stuff, and I don't talk very frequently to clients that aren't standard browswers. If I did, I think I would have a lot more to gain from this release.

michaelneale 19y ago
That is probably a good thing. Rails is a great fit for what it does, a 2.0 danger was to do beyond its strengths. It seems to have evolved nicely. I look forward to using it. As for the questions about the lack of "scalability" improvements, I don't really care. Its not needed for what I use it for anyway (and probably the same for most people).

jraines 19y ago

One new thing is the ActiveREST module, which provides a lot of neat support for creating RESTful services. Between this and Ruby 1.9 there's some fun new stuff for RoR folks to play with.

qaexl 19y ago

The change between 1.1 and 1.2 was much more disruptive than the change between 1.2 and 2.0. The biggest changes are in reworking the RESTful controllers and cutting down the cruft. 2.0 is more polished and shinier now. The 2.0 release may be coming in close with the upcoming Ruby 2.0 release, which will be highly disruptive (YARV bytecode backend), though I'm not sure if Rails 2.0 will work fine without any changes in Ruby 2.0. Besides, I'm not really sure when Ruby 2.0 is coming out.

russ 19y ago
I've been hearing that by Xmas for Ruby2 and the Rails guys have been doing quite a bit of work to make sure Rails2 is compatible with the upcoming Ruby release. I'm not sure how much will need to change, but they have indeed been working towards making it compatible.

palish 19y ago

Keep in mind that as a tool approaches "optimal", it needs to be changed less and less. So if Rails' new features don't justify the jump to "2.0", its stability and user-adoption may.