Ask HN: Updated recommendation on Rails versus Django?

Re:Ask HN: Updated recommendation on Rails versus Django? by benatkin on Sunday July 19, 2009 @02:09PM (#713192)

Here's what I've found so far after starting a small Django gig (I already knew a fair bit about Rails):

- Rails has built-in migration support

- Rails has better support for APIs

- Django has some neat stuff in contrib including authentication and an admin interface

- Django has "pluggables" -- downloadable apps that can be snapped in just like the admin interface. Rails has engines, but they're new and not as mature as pluggables.

[ Parent | on HN ]

Re:Ask HN: Updated recommendation on Rails versus Django? by mccutchen on Sunday July 19, 2009 @02:59PM (#713235)

> Rails has better support for APIs

What does this mean?

[ Parent | on HN ]

Re:Ask HN: Updated recommendation on Rails versus Django? by benatkin on Sunday July 19, 2009 @09:52PM (#713742)

To be specific, Rails has better support for providing XML and JSON APIs. One place where it has better support is serialization. In rails, there is an :include parameter to control whether to include objects from associations (e. g. comments in a post), that is available both on to_xml or to_json. I don't see an option for Django that does the same thing.

http://api.rubyonrails.org/classes/ActiveRecord/Serializatio... http://docs.djangoproject.com/en/dev/topics/serialization/

[ Parent | on HN ]

Re:Ask HN: Updated recommendation on Rails versus Django? by qhoxie on Sunday July 19, 2009 @09:06PM (#713690)

Probably talking about ready-built libraries. Poorly worded though.

[ Parent | on HN ]