Forgot your password?
typodupeerror
Programming

Rails 3.0 Released 110

Posted by CmdrTaco
from the really-right-rails dept.
An anonymous reader writes "After two years of gestation, 4 betas, 2 release candidates and thousands of commits by 1600+ contributors, the result of the succesful merge of the Merb and Rails frameworks (and teams) is now out and ready to transport your web applications on all new shiny tracks."
This discussion has been archived. No new comments can be posted.

Rails 3.0 Released

Comments Filter:
  • Re:Too many changes? (Score:4, Informative)

    by Anonymous Coward on Monday August 30, 2010 @09:12AM (#33414096)

    2.3.x is still supported, actually they're working on 2.3.9 as we speak.
    It's true that the Rails eco system moves forward at a good pace, but that's a good sign to me. it means ideas are brewing and accepted.
    A sign of good health :)

  • Great release (Score:5, Informative)

    by jgeiger (1356045) on Monday August 30, 2010 @09:13AM (#33414110)
    A lot of the changes have made the code much more modular. You don't need to include everything if you don't need it. This also allows you to plug in other database adapters if you want. One of the nice routing changes allows you to call Rack or Sinatra applications from within your Rails application. I'm really looking forward to using this going forward.
  • Re:Too many changes? (Score:4, Informative)

    by ojustgiveitup (869923) on Monday August 30, 2010 @10:03AM (#33414520)
    They've been working on Rails 3 for more than a year now... not really so rapid. For instance two versions of Ubuntu have come out since then.
  • by Anonymous Coward on Monday August 30, 2010 @10:31AM (#33414830)

    Python a favourite of slashdot? Woa, where did the whitespace-as-indentation haters go? Where are the pry-my-curly-braces-from-my-dead-fingers people? Is this some sort of alternative universe I'm in?

  • by SanityInAnarchy (655584) <ninja@slaphack.com> on Monday August 30, 2010 @02:16PM (#33417704) Journal

    One assumption is that the Rails community -- as you said, "straight from the top" -- embraced unsafe GETs and tried to block GWA in order to keep using unsafe GETs.

    I don't know if this was ever true, but it hasn't been true for at least two years, probably longer. Rails has embraced REST to an obsessive degree, which means not only are GETs never used for unsafe operations, but if your UA supports PUT and DELETE, Rails will accept those. (If not, PUT and DELETE are emulated over POST -- still not GET.) I met all kinds of fascinating people at Railsconf this year, and we disagreed on all sorts of things, but I seriously don't remember a single person arguing that REST was a bad idea, certainly not that unsafe GETs are a good thing.

    jemmyw was the reply which pointed this out to you, though not in as much detail.

    So, anyone who was calling GWA "scary" because of this was wrong and either not representative of the Rails community, or you're telling us a story from at least 3-5 years ago, which is a long time in Rails development time.

  • by Per Wigren (5315) on Monday August 30, 2010 @03:27PM (#33418468) Homepage

    and significant challenges making it play nice with Apache in a manner comparable to mod_php. (has mod_ruby come of age, yet? ;3)

    Passenger [modrails.com] is what you're looking for.

  • by Jane Q. Public (1010737) on Monday August 30, 2010 @04:11PM (#33419000)
    First, I apologize for getting you mixed up with the person who wrote that Rails had implemented PUT and POST backward, which simply isn't the case. That's what I was mainly referring to when I wrote that you were wrong. But do have another issue with the things you wrote.

    You equated one or maybe a few specific people with the "Rails community". David Heinemeier Hansson might be the original author of Rails, but he is not -- even remotely -- the "Rails community", nor is 37 Signals. And you made that error not once, but twice.

    First, you describe how GET was often used for unsafe operations (a good description of that is available HERE [moertel.com]). However, using the link_to method as described is hardly "standard practice". In fact it is anything but, regardless of whether DHH and 37 Signals have used it that way. In general, link_to was designed simply for navigating among web pages. The fact that it allows GET to be used for unsafe operations is unfortunate, but the fact is that I know few people who would ever actually use it that way. As someone else mentioned in one of the replies to that post, any framework can be abused. That is generally the fault of the developer, not the framework.

    Further, the "rails developers" you accuse of being immature for complaining about it consisted of -- who else? -- David Heinemeier Hansson. Not the "rails community". If you were not aware of this already, then let me inform you: that was 5 years ago and since then the "rails community" itself, on more than one occasion, has derided DHH for his frequent immature behavior.

    Your last point, about the word "professional", was again a reference to DHH personally and not "the rails community". Further yet, what he was referring to was the way the word "professional", like some other phrases, has been abused... he was not insulting professionals. In fact he made no references at all to "professionals" or "professionalism".

    In summary, you are guilty of accusing a whole multitude -- thousands of people -- of being immature, almost entirely because of the actions of one person. Remind me again... who is being immature here?
  • by xiong.chiamiov (871823) <xiong.chiamiov@nOspaM.gmail.com> on Monday August 30, 2010 @04:35PM (#33419336)
    Ruby 3.0 is a long ways off. You probably want Rails 3.0 and Ruby 1.9.

/earth: file system full.

Working...