←back to thread

310 points brylie | 3 comments | | HN request time: 0.411s | source
1. sroerick ◴[] No.43512820[source]
As a guy with a lot of hours into Django, I will echo that I don’t quite understand the “why” here.

I think there’s a number of areas where Django falls a bit short and other web frameworks excel. For example, task workers are not first class citizens and require Celery or another task manager. REST APIs are a similar situation. Celery and Django REST are great, but they do feel a little ham handed. I’ve seen other frameworks handle this in ways that really seem to work great.

I guess auth is prioritized here? But I actually like the barebones Django auth and find it useful in many situations where I don’t need full OAuth.

I’m not saying this isn’t needed and it looks cool and nice - but for the use cases where I’ve struggled with Django, it seems like this would actually increase complexity, as the 3rd party ecosystem would obviously not be robust.

It looks like the author has a perfectly good workflow and use case for this, but it’s not clear from the homepage or the “about” page linked elsewhere in the comments exactly what this is for

replies(2): >>43513126 #>>43514056 #
2. phonon ◴[] No.43513126[source]
FYI https://github.com/RealOrangeOne/django-tasks will be included in Django once it is ready.
3. graemep ◴[] No.43514056[source]
Django have been by bread and butter work for a long time, and I do not really get the point of this.

There are bits I agree with but nothing like enough to be worth losing compatibility with third party packages.