The commit parameter is a pain in the backside when it comes to rails but I would have thought most people would know how to fix this anyway. It's a simple HTML issue, not really a Rails issue.
The commit mostly fixes that particular issue (and is included in 3.0.7), but as the article point out Rails 3 AR performance still needs quite a bit of work.
Humorously I joked about it hitting HN during the talk, and then it actually did. We as developers can't resist something that'll quantify for us whether we're good at writing software, even when we know it's flawed.
I'm sorry if you thought this was 'drama,' just trying to make sure that someone doesn't think that this is officially supported by the Rails team or that I'm speaking for anyone. Frankly, I've been running around at Ruby conferences saying "If you want old versions of Rails supported, you should be paying someone to do it," and I think Rails LTS is great, in a personal capacity.
Not sure this is what you're getting at. I agree with the author though, this aspect of Rails bothered me quite a bit. Knowing that working on a Rails project meant I could magically generate ranges from dates because of ActiveSupport was unsettling - it made me wonder what else was non-native behaviour and waiting to trip me.
reply