It seems weird to want NextJS to be a batteries-included backend framework, when it's not even a batteries included frontend framework. NextJS offers SSR and a router and that's about it, if you need client side data fetching you will still use React Query / SWR, if you need heavy client state management you'll use Redux / Zustand, you probably want an UI library so you'll have to install Bootstrap / HeadlessUI / Radix etc. Everytime you start a NextJS project you must go through library shopping even for frontend stuff
Full-stack javascript sounds cool for small side projects but I want to have the freedom to write my backend in wathever technology I want, and I think many company do as well. I think the focus should be a robust frontend framework with modern features (SSR, data fetching, client routing etc.) and I'm hoping SvelteKit will be this framework
I agree that maybe NextJS could do with more 'batteries' included, for things like Auth, and could do a better job for providing (lowercase H) hooks for client-side data fetching (given its existing get*Props APIs), but I think it's realtively wise for NextJS to not have much of a say for things like UI component libraries. I don't think it makes sense for NextJS to ship with like Bootstrap - I don't want to use it!
> Full-stack javascript sounds cool for small side projects but I want to have the freedom to write my backend in wathever technology I want
You do have this freedom though! Doing full-stack javascript is a choice you can make with that freedom.
I do not even begin to suggest in my comment that NextJS is batteries-included, nor that I want it to be. Maybe you're addressing someone else's comments.
Full-stack javascript sounds cool for small side projects but I want to have the freedom to write my backend in wathever technology I want, and I think many company do as well. I think the focus should be a robust frontend framework with modern features (SSR, data fetching, client routing etc.) and I'm hoping SvelteKit will be this framework