News for hackers. Stuff that matters.
Re:Thoughts about Rails from a Django guy by bad_user on Sunday July 25, 2010 @06:20PM (#1546492)
> As somebody who has used both Rails and Django commercially ... In Django you have to migrate manually, or lose data

If you've been using Django "commercially", then how come you haven't heard of South? ... http://south.aeracode.org/

Everybody in the community that wants migrations is using it.

> Why not go all the way to a usable and powerful template language?!

In Django components are more decoupled than in Rails. You can replace that templating engine.

Also, Django's templating system is really not that inflexible or hard to use ... quite the contrary, it comes with many things out-of-the-box that aren't standardly provided by other web frameworks ... like the ability to cache page fragments.

Re:Thoughts about Rails from a Django guy by jules on Sunday July 25, 2010 @06:48PM (#1546534)
Of course those are valid points but we are comparing default feature sets here. Otherwise Rails has a crippled template language, database generated from model and automatic admin too.

Have you actually used Rails? Rails has fragment caching built in and you can use a different template engine very easily (just install the engine xyz you want to use and write templates with extension .xyz instead of .erb)

Re:Thoughts about Rails from a Django guy by catch23 on Sunday July 25, 2010 @08:46PM (#1546727)
It's kind of odd that the default subsystems that come with Django are always replaced with something else -- why doesn't Django include some sane defaults instead?
Re:Thoughts about Rails from a Django guy by bad_user on Monday July 26, 2010 @04:47AM (#1547487)
This implies that Rails has "sane defaults".

From my experience that's hardly the case ... ActiveRecord (pre 3.0 at least) sucks big monkey balls compared to Django's ORM. And Rails also doesn't have anything like the forms API in Django.