7 ms·
"Django was born in the fall of 2003, when the web programmers at the Lawrence Journal-World newspaper, Adrian Holovaty and Simon Willison, began using Python t
by jh3 11y ago
"Django was born in the fall of 2003, when the web programmers at the Lawrence Journal-World newspaper, Adrian Holovaty and Simon Willison, began using Python to build applications. It was released publicly under a BSD license in July 2005. The framework was named after guitarist Django Reinhardt."
Source: https://en.wikipedia.org/wiki/Django_(web_framework)#History https://en.wikipedia.org/wiki/Django_(web_framework)#History
- servercobra 11y agoRight, but any examples of it feeling crufty? Personally I think the templating system is less and less useful because I'm serving single page apps that I don't really benefit from serving from Django any more (or are Angular and the variable syntaxes conflict with each other)
- ralmidani 11y agoDjango has outgrown its humble beginnings. I am building a fairly sophisticated single-page business application using Django along with Django REST Framework, and have yet to run into a situation that made Django feel "crufty."
- dcgoss 11y agoDjango REST Framework is excellent.
- karkucik 11y agoAnd quite slow
- techdragon 11y agoI can't even begin to imagine what your doing with it that makes you think it's slow. Links or references to documented slowness?
- pbreit 11y agoWell, obviously an SPA would not run into any of the cruftiness since you're just using Django as a "dumb pipe" to the DB.
- ralmidani 11y agoMy point is Django is not limited by the fact that it was initially conceived as a framework for serving static web pages.
- mastazi 11y agoNot all SPAs are based on the DB+"dumb pipe"+SPA stack, sometimes you need to process things on the server, based on your business requirements and/or performance considerations. Sometimes the processing done in that layer can be quite significant. If that is your need, both Django itself (using JsonResponse and serialization objects) and Django REST Framework allow you to do so much more than dumb piping.
- brianwawok 11y agoSo as a Scala Play dev... Trying to get the user stuff to work with email as username and still work on the admin page? Super crufty. Overall very good docs though :)
- zeemonkee3 11y agoThat's not been an issue for several years (since Django 1.5(?) introduced custom user models). Drop in a custom admin form and you're done.
- brianwawok 11y agoThat is not true with current (1.9). Drop in a custom user model and a) Better be a brand new project at all b) You need to muck with the user manager also c) How do you fix up the admin module? I have yet to see a fully fixed up admin module for the custom user. I am not a Django pro so happy to be proved wrong. But take a default app, and record all steps to make the user model work (including password reset, login, logout, admin page). If that doesn't feel crufty to you I am not sure what cruft is.
- pbreit 11y agoNot my experience either. And in 2016, email-as-username should be default and work flawlessly out of the box.
- zeemonkee3 11y agoFair enough. Here's some code I wrote for a side project a couple of years ago - it was a side project, not meant for real world production, and it's a couple Django versions behind, so no guarantees as to quality, but should give you an idea: https://github.com/danjac/ownblock/blob/master/ownblock/ownblock/apps/accounts/admin.py https://github.com/danjac/ownblock/blob/master/ownblock/ownb...
- deleted 11y ago[deleted]