Slashdot Mirror

← Back to Stories (view on slashdot.org)

Rails 2.1 Is Now Available

Posted by kdawson on from the blood-on-the-tracks dept.

slick50 writes "Rails 2.1 is now available for general consumption with all the features and fixes we've been putting in over the last six months since 2.0. We've had 1,400 contributors creating patches and vetting them. This has resulted in 1,600+ patches. And lots of that has made it into this release. The new major features are: time zones (by Geoff Buesing), dirty tracking, Gem dependencies, named scope (by Nick Kallen), UTC-based migrations, and better caching. As always, you can install with: gem install rails Or you can use the Git tag for 2.1.0."

3 of 71 comments (clear)

  1. Re:I love Ruby and Rails, don't get me wrong... by setagllib · · Score: 2, Interesting

    I really don't know how Ruby gets away with having such bad encoding support. Java and Python both solved that problem long ago, and Python 3 gets even more Java-like by having the standard string type be unicode. Heck, even C++ frameworks solved it. Meanwhile Ruby makes encodings just as hard as in C, if not harder.

    --
    Sam ty sig.
  2. Re:I love Ruby and Rails, don't get me wrong... by JanneM · · Score: 2, Interesting

    That's a bit weird. AFAIK, Ruby 1.9 takes the encoding you use system-wide as the default - if the "2009" above is interpreted as 8-bit ascii, it means that's the encoding for the environment you start ruby in.

    --
    Trust the Computer. The Computer is your friend.
  3. Re:Wt by bertilow · · Score: 3, Interesting

    Brilliant! The WT page states that WT "Generates standards compliant HTML or XHTML code". But the page itself is not valid, and the gorram "Hello world"-example is also not valid, and - as it seems - the same goes for all other WT examples on that site! No, I don't think I will use WT.