On 4/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> You have good friends, they are giving you great advice. Rails is in
> it's second production release, has a huge following, and a number of
> books to help document it. Django is still in a major development
> phase and is geared towards early adopters and framework developers at
> the moment.
Don't tell that to Scripps or to any of the other large, conservative
companies that are quietly deploying Django ;)
Seriously, though, I think this is a misconception. Rails has reached
a *public* 1.0, yes, but it was running in production environments
long before anyone outside of 37Signals knew about it. Similarly,
though Django hasn't reached a public 1.0 yet, it was running in
production environments long before anyone outside the newspaper
industry knew about it. What Django's going through right now is a
period of expansion and refinement, as people who are finally getting
a look at it come in with lots of smart ideas to make it even better.
> Many developers have opted to start there new projects
> with the newest unstable development branch ("Magic Removal"/.92) so
> they can reduce the pain of a .91 migration. This is fine, but you
> need to be prepared to change with it. I would recommend doing the
> Django tutorial, but would really think long and hard about starting a
> new project with it until .92 or later is released.
I'm not sure what we need to be "prepared to change with"; all the
major changes which will be made are and have been documented for
quite some time. Anyone starting out on magic-removal should know by
now exactly what to expect.
> This is nice if you are not used to dealing with SQL directly, but
> really isn't that advantageous if you are already using SQL on a
> regular basis. In fact, it does present some issues with an evolving
> schema. However many of those issues are being addressed with new
> tools like syncdb in the mysterious .92 release.
'manage.py syncdb' in magic-removal has nothing to do with evolving
database schemas.
> Ajax is a large pill to swallow, and Django is way behind Rails at the
> moment in that department.
That depends on your philosophy with respect to how AJAX should be used.
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
