> Deploying NextJS stuff on Vercel, while maybe dev experience friendly, is not a visitor friendly thing to do. The amount of websites, that merely show a whit

> Deploying NextJS stuff on Vercel, while maybe dev experience friendly, is not a visitor friendly thing to do. The amount of websites, that merely show a white screen, when you don't allow arbitrary JS to run ... And of course with allowing tons of JS comes tons of tracking. That has nothing to do with deploying on Vercel. In fact, deploying on Vercel and using NextJS _should_ allow developers to do exactly the opposite: provide javascript-enhanced [0] websites instead of javascript-only, with server-side rendering with low latency since the servers are right next to the user. It's just most developers are lazy, and for some reason the recommend practice is to do data fetching on the client, even though data fetching on the server is extremely trivial in NextJS [1][2]. Also, Vercel doesn't force you to use NextJS, in fact they hired Rich Harris which is the genius behind Rollup and Svelte. SvelteKit also allow for a hybrid javascript-enhanced approach with remix-inspired form actions [3] and hybrid data loading [4]. [0]: https://react.dev/reference/react-dom/hydrate https://react.dev/reference/react-dom/hydrate [1]: https://nextjs.org/docs/basic-features/data-fetching/get-server-side-props https://nextjs.org/docs/basic-features/data-fetching/get-ser... [2]: https://nextjs.org/docs/basic-features/data-fetching/get-static-props https://nextjs.org/docs/basic-features/data-fetching/get-sta... [3]: https://kit.svelte.dev/docs/form-actions https://kit.svelte.dev/docs/form-actions [4]: https://kit.svelte.dev/docs/load#universal-vs-server https://kit.svelte.dev/docs/load#universal-vs-server