Why critics of Rails have it all wrong (and Ruby's bright multicore future)

Re:Why critics of Rails have it all wrong (and Ruby's bright... by bascule on Thursday September 13, 2012 @07:20PM (#4519186)

The release notes for Django 1.4, for example, list support for both Time Zones and Selenium.

Time Zones were added to Rails 2.1 in 2008. selenium-on-rails also debuted in 2008.

Does it not seem strange to you that it took 4 years after Rails for Django to get these features?

[ Parent | on HN ]

Re:Why critics of Rails have it all wrong (and Ruby's bright... by ch0wn on Friday September 14, 2012 @05:10AM (#4520840)

There were plenty of extensions that allowed you to use Selenium with Django, I maintained one of them. Django is fairly conservative about including new features into the core that work well as extensions. And this is something I value a lot.

The time zone support, though, was really overdue.

[ Parent | on HN ]

Re:Why critics of Rails have it all wrong (and Ruby's bright... by dscrd on Friday September 14, 2012 @03:46AM (#4520614)

Really, if you wanna complain about something that's in Rails and not in Django properly, talk about database migrations.

[ Parent | on HN ]

Re:Why critics of Rails have it all wrong (and Ruby's bright... by hackerboos on Friday September 14, 2012 @08:38AM (#4521306)

South...but I agree that database migrations should be part of the Django core.

[ Parent | on HN ]

Re:Why critics of Rails have it all wrong (and Ruby's bright... by Styck on Friday September 14, 2012 @06:35AM (#4521012)

Not really a fair feature comparison. If db migration wasn't in Rails, ActiveRecord wouldn't work the way it does. You can't say the same about Django's ORM.

[ Parent | on HN ]