4 ms·
Interesting, I take the opposite approach: As your project starts to grow, you end up ripping out the "batteries" of django and implementing other modules. The
by neurosnap 11y ago
Interesting, I take the opposite approach: As your project starts to grow, you end up ripping out the "batteries" of django and implementing other modules. The most notable one would be SQLAlchemy.
- rlander 11y agoYup. I switched to Flask mostly because I always ended up ripping Django apart: - Jinja instead of Django templates. - Custom (and sane) class-based views instead of Django's disgusting defaults. - Custom class-based settings. - There's no way to define app-only middleware in Django. Flask blueprints make it trivial. However, 10 years later and no framework has come close to Django's true strength: built-in admin.
- mtbcoder 11y agoYou don't have to use Django's class-based generic views either. Nothing wrong with just inheriting from the base View if you really want.
- emidln 11y agoYou can also just skip the infinite inheritance and implement function-based views.
- Igglyboo 11y agoJust an FYI, the newest version of Django (1.8) now supports Jinja or Django templates by default and you can plugin other templating engines if you want.
- Zopieux 11y agoDid you try to use Jinja2 templates in 1.8? There is hell of a bootstrapping to do until you can actually start working with these. Don't even try to use both at the same time within the same project. You'll end up crazy before you can make Django load the right template.
- Igglyboo 11y agoNo I haven't, still on Django 1.6 at work but I keep up with the newest developments. That's a shame, from what I read it sounded like it was just a simple config setting that would allow you to use Jinja over Django templates.
- dev360 11y agoInteresting. Almost every experienced Django dev I know throws out the admin on their projects nowadays.
- hackerboos 11y agoIn favour of what?
- andybak 11y agoI don't.
- welder 11y agoExactly. I think that's why Flask needs more experienced devs for larger sites. This also means it's easier to hire Django devs.
- collyw 11y agoI am curious about this. I like Djangos ORM for the basic stuff, but it doesn't work on even moderately complex queries (conditional aggregates are a serious loss). Would I gain much by going to SQL Alchewy over just using raw SQL, which is what I do at the moment? (bearing in mind replacing the Python ORM completely, and you will loose the admin, which I use heavily).
- huxley 11y agoIt's a pretty recent development, but have you tried Django 1.8's Conditional Aggregation and Conditional Expression features? https://docs.djangoproject.com/en/1.8/ref/models/conditional-expressions/#conditional-aggregation https://docs.djangoproject.com/en/1.8/ref/models/conditional...
- collyw 11y agoNot yet, I usually stay with the latest stable version. Sounds good though. Its been long overdue.