3 ms·
The problem with something like login/registration is that on the one hand it's a repetitive task, on the other it's something that ends up being highly customi
by zeemonkee 16y ago
The problem with something like login/registration is that on the one hand it's a repetitive task, on the other it's something that ends up being highly customised for each application.
My experience with Django is that you generally start with the generic login and registration views, but quickly end up ditching them when you need something just a bit different. I'm not sure what would be a better solution, and I'm not sure there is one. I've yet to see a solution that is neither a) too complex (AuthKit) nor too simplistic (Django).
Form processing and REST are a bit more low level and should be achievable by a modestly-sized framework or library.
- stevenwei 16y agoI agree that the end implementation of a User login and registration system will be highly customized for each application. However, I think there is a TON of reusable code out there that is shared across apps: simple things like setting properly salted and hashed passwords, providing a password reset mechanism, and a base user object with permissions and groups. Django gets a lot of this stuff right, what they get wrong is the complete lack of customizability which means you need to throw everything away once you go outside the box. A few simple base classes that could be extended and overridden with custom fields would solve that problem entirely - the reason Django doesn't provide this (IIRC) is because the built in auth system was written before their ORM properly supported inheritance.
- zeemonkee 16y agoClass-based generic views would go a long way as well; Django's generic views are pretty useless in their current form.