TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Why I Ditched Django for NextJS

3 pointsby rareitem11 months ago

1 comment

necovek11 months ago
This mostly seems centered on two things:<p>* Since you have to use JS&#x2F;TS for the frontend, you might as well use it for everything<p>* When you need common, modern functionality, you can find it&#x27;s already there in NextJS, but missing in a traditional stack<p>But really, both of these could be addressed by something like <a href="https:&#x2F;&#x2F;google.github.io&#x2F;mesop&#x2F;" rel="nofollow">https:&#x2F;&#x2F;google.github.io&#x2F;mesop&#x2F;</a><p>I am intrigued by the static&#x2F;dynamic reusing even more code, so I&#x27;ll look into NextJs to understand the benefits better (compared to classic templating or SPA-approach).<p>Still, I&#x27;d note that many web site types do not need to be &quot;applications&quot;.