Recent searches
Search options
A little late because it was the kids' birthday yesterday, this month's Stack Report, some thoughts on Django Core.
https://buttondown.com/carlton/archive/thoughts-on-djangos-core/ #Django #TheStackReport
@carlton Django tasks is so double, great that Django gets support, but celery and/or rq now also work fine, so afraid we'll end up with django-celery-tasks and django-rq-tasks (and maybe many more) which then adds another dependency to maintain by someone... or it goes like static files did, where people want it pluggable so they can use their own preferred flavour and then everyone ends up using the default anyway and you have all this abstraction you have to maintain.
@carlton@fosstodon.org@hvdklauw The tasks interface is pretty simple. Clients can use it independently of the backend. Hopefully there will be various implementations. I've be using Django-Q forever, having a django.tasks backend for that will allow me to migrate to the new API in my own time. I think that's pretty cool.