Laravel’s whole approach to the frontend feels miles ahead. It offers opinions right in the docs and in the project generation for how to set up modern JS tooling. I have to go to third parties like @coryzue.com’s articles about it or third party libraries like django-vite to get the same thing.
I understand/appreciate that the Django docs want to stay agnostic to the changing whims of the frontend. But, I feel like there is a middle ground -- link to high-quality guides like Cory’s.
Either that happens from the docs, i.e. they are helpful, or devs are left to figure it out on their own.
What @davegaeddert.com is doing with https://plainframework.com is interesting though and a peek at what an opinionated view on this would look like in Django core.
Agreed, I’ve been keeping an eye on it. Interested to see how it goes with one person making cohesive decisions instead of "decision by community” (which is great in other ways).
Comments
Either that happens from the docs, i.e. they are helpful, or devs are left to figure it out on their own.
It’s also the one major backend framework I see featured as an integration in JS tool docs eg Tailwind and Vite come to mind