Why I Ditched Django for NextJSbillprin.com 3 pointsrareitem2 years ago1 commentSaveHideCopy link On HNComments−necovek2yThis mostly seems centered on two things:* Since you have to use JS/TS for the frontend, you might as well use it for everything* When you need common, modern functionality, you can find it's already there in NextJS, but missing in a traditional stackBut really, both of these could be addressed by something like https://google.github.io/mesop/I am intrigued by the static/dynamic reusing even more code, so I'll look into NextJs to understand the benefits better (compared to classic templating or SPA-approach).Still, I'd note that many web site types do not need to be "applications".
Comments
This mostly seems centered on two things:
* Since you have to use JS/TS for the frontend, you might as well use it for everything
* When you need common, modern functionality, you can find it's already there in NextJS, but missing in a traditional stack
But really, both of these could be addressed by something like https://google.github.io/mesop/
I am intrigued by the static/dynamic reusing even more code, so I'll look into NextJs to understand the benefits better (compared to classic templating or SPA-approach).
Still, I'd note that many web site types do not need to be "applications".