I'm loving Rails 3 Beta 1, but I'm surprised they've broken Ruby 1.9.1 compatibility with today's release. Not to be a hater, but I don't see the point of releasing a new beta after introducing a regression so serious that it causes the framework to segfault on the current stable Ruby.
I don't think it's a bad thing. Ruby 1.9.1 needs to go. There are a number of bugs and quirks in 1.9.1 which have been fixed in 1.9.2. E.g. while developing Phusion Passenger I've noticed some VM deadlock bugs, all of which are now fixed.
It shouldn't even be possible to segfault an interpreted language like Ruby, let alone the "current stable" version. Sounds like it's Ruby-core's problem, not Rails-core's.
That said, I agree with you, it's strange. But I do think it's good they're pushing so hard for 1.9.2.
It shouldn't even be possible to segfault an interpreted language like Ruby, let alone the "current stable" version. Sounds like it's Ruby-core's problem, not Rails-core's.
I clicked through and extracted all the changes since beta 1. This is probably only useful for people who have already spent some time with the first beta but haven't been following development since then:
* Whole new API added with tests. See base.rb for full details. Old API is deprecated.
ACTIONPACK
* #concat is now deprecated in favor of using <%= %> helpers [YK]
* Block helpers now return Strings, so you can use <%= form_for @foo do |f| %>.
<% form_for do |f| %> still works with deprecation notices [YK]
* Add a new #mount method on the router that does not anchor the PATH_INFO
at the end [YK & CL]
* Create a new LookupContext object that is responsible for performantly
finding a template for a given pattern [JV]
* Removed relative_url_for in favor of respecting SCRIPT_NAME [YK & CL]
* Changed file streaming to use Rack::Sendfile middleware [YK]
* ActionDispatch::Request#content_type returns a String to be compatible with
Rack::Request. Use #content_mime_type for the Mime::Type instance [YK]
* Updated Prototype to 1.6.1 and Scriptaculous to 1.8.3 [ML]
* Change the preferred way that URL helpers are included into a class[YK & CL]
# for all helpers including named routes
include Rails.application.router.url_helpers
# for just url_for
include Rails.application.router.url_for
ACTIVEMODEL
* #new_record? and #destroyed? were removed from ActiveModel::Lint. Use
persisted? instead. A model is persisted if it's not a new_record? and it was
not destroyed? [MG]
* Added validations reflection in ActiveModel::Validations [JV]
Model.validators
Model.validators_on(:field)
* #to_key was added to ActiveModel::Lint so we can generate DOM IDs for
AMo objects with composite keys [MG]
ACTIVESUPPORT
* Reduced load time by deferring configuration of classes using
ActiveSupport::on_load(:component_name) [YK]
* Rename #metaclass to #singleton_class now that ruby-core has decided [JK]
* New assertions assert_blank and assert_present. #4299 [Juanjo Bazan]
* Use Object#singleton_class instead of #metaclass. Prefer Ruby's choice. [Jeremy Kemper]
* JSON backend for YAJL. Preferred if available. #2666 [Brian Lopez]
RAILTIES
* Session store configuration has changed [YK & CL]
It's because the Rails team knows they are about to lose a lot of people to Padrino. Got to act fast before people realize how much of a better framework it is!
Lame. How old are you, 12? I find it "interesting" that developers of competing software usually get along fine, but for some reason the users feel the need to attack, flame at and troll at each other.
Perhaps my remark was a bit snide but I was not attacking or flaming anyone.
It's not like I called the rails team assholes or said rails sucks. I dont think either is the case - Rails pays my bills right now and I love it, but after playing with Padrino for 2 weeks all I can say is that my Rails days are numbered.
These guys really nailed everything - speed, cleanliness and common sense. Superior routing, mountable apps done right and a killer admin app out the box are just a few added perks. Top it off with a DSL that is far more Rubyish than Rails (and source code that is MUCH easier to read) and what's not to love?
Besides, a little friendly competition is GOOD for our community.
