I would say it is a bit more convoluted than any backend framework, not just PHP.
The reason I think that is because Nextjs is a framework with heavy frontend roots.
The biggest difference between frontend and backend is that frontend has a visual focus. And backend is a connector between the storage of data and the frontend, whatever that frontend might be.
Another negative point is that is a single frontend framework. That is why Nuxt and Sveltekit exist.
Other javascript backend frameworks like Nest and Astro allow you to pick the frontend framework.
The biggest selling point of javascript on the server is a single language codebase. And that also makes it possible to use functions in the backend and frontend.
The reason I keep using "traditional" backend languages is that they are more robust and fit for the task than javascript.
Ah, that makes a lot of sense now — especially knowing you've been writing about PHP.
Honestly, I think we're on the same page: both PHP (and other classic backend stacks) and Next.js are trying to solve the same problems — just through very different cultural and tooling lenses.
Where I think it gets tricky is that modern frontend frameworks often try to subsume the backend — but without the maturity that backend ecosystems (like PHP’s or Rails') have built over decades.
In that sense, Next.js isn’t just “like PHP” structurally — it's like PHP in its early, chaotic days, but rebranded through React.
So yes — we may disagree on nuance, but I think we're both reacting to the same deeper truth: simplicity and robustness are being sacrificed for DX theater.
Would love to read more of your PHP pieces, btw. Got a link to one you'd recommend?
I would not say Nextjs is as chaotic as early PHP. The javascript frameworks learned from the backend frameworks.
The biggest problem in the javascript community as I see it, is that most people live on their framework of choice island. Which gave us Next and Nuxt solutions, while Nest and Astro are more in tune with the common backend structure.
I'm not sure what to recommend, with my content I want to explore things that are less known or ideas I have and experiment with. Just pick something you like when you read the title.
Really appreciate your thoughtful take — and I totally agree that JS frameworks often drift into isolated paradigms.
That’s actually what inspired me to start working on something called Type.ts — a framework not based on freedom of expression, but on enforced correctness.
It’s not about flexibility. It’s about writing the only correct code, every time.
Here’s the core idea:
Type.ts isn’t a framework of freedom.
It’s a culture of correct structure — enforced through syntax, routing, CI, and thought.
One route = one file (user.post.ts = POST /user)
defineAPI() guarantees exact structure, types, and execution
Thank you so much for taking the time to respond so thoughtfully.
Your comment didn’t just challenge my perspective — it helped me grow.
You reminded me that real innovation isn’t just about critique, but about conversation, reflection, and curiosity.
It’s easy to fall into the trap of “provocative takes,” but your insight pulled me back into the kind of dialogue that actually moves us forward as developers.
Deeply grateful for that.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would say it is a bit more convoluted than any backend framework, not just PHP.
The reason I think that is because Nextjs is a framework with heavy frontend roots.
The biggest difference between frontend and backend is that frontend has a visual focus. And backend is a connector between the storage of data and the frontend, whatever that frontend might be.
Another negative point is that is a single frontend framework. That is why Nuxt and Sveltekit exist.
Other javascript backend frameworks like Nest and Astro allow you to pick the frontend framework.
The biggest selling point of javascript on the server is a single language codebase. And that also makes it possible to use functions in the backend and frontend.
The reason I keep using "traditional" backend languages is that they are more robust and fit for the task than javascript.
Ah, that makes a lot of sense now — especially knowing you've been writing about PHP.
Honestly, I think we're on the same page: both PHP (and other classic backend stacks) and Next.js are trying to solve the same problems — just through very different cultural and tooling lenses.
Where I think it gets tricky is that modern frontend frameworks often try to subsume the backend — but without the maturity that backend ecosystems (like PHP’s or Rails') have built over decades.
In that sense, Next.js isn’t just “like PHP” structurally — it's like PHP in its early, chaotic days, but rebranded through React.
So yes — we may disagree on nuance, but I think we're both reacting to the same deeper truth: simplicity and robustness are being sacrificed for DX theater.
Would love to read more of your PHP pieces, btw. Got a link to one you'd recommend?
I would not say Nextjs is as chaotic as early PHP. The javascript frameworks learned from the backend frameworks.
The biggest problem in the javascript community as I see it, is that most people live on their framework of choice island. Which gave us Next and Nuxt solutions, while Nest and Astro are more in tune with the common backend structure.
I'm not sure what to recommend, with my content I want to explore things that are less known or ideas I have and experiment with. Just pick something you like when you read the title.
Really appreciate your thoughtful take — and I totally agree that JS frameworks often drift into isolated paradigms.
That’s actually what inspired me to start working on something called Type.ts — a framework not based on freedom of expression, but on enforced correctness.
It’s not about flexibility. It’s about writing the only correct code, every time.
Here’s the core idea:
user.post.ts=POST /user)defineAPI()guarantees exact structure, types, and executionsafe(),defineError())type dev,type checkenforce the philosophydefault exportandletare forbidden — by designIt’s not just a tool. It’s a belief system embedded in code.
I’m experimenting with this not to compete, but to explore what happens when we make the structure the culture. type.ts github
Thank you so much for taking the time to respond so thoughtfully.
Your comment didn’t just challenge my perspective — it helped me grow.
You reminded me that real innovation isn’t just about critique, but about conversation, reflection, and curiosity.
It’s easy to fall into the trap of “provocative takes,” but your insight pulled me back into the kind of dialogue that actually moves us forward as developers.
Deeply grateful for that.