6 ms·

Awesome! Too bad Next.js will never profit from these incredible community efforts, because Vercel suffers from NIH.

pjmlp 7mo ago
They have the enterprise partners that make Next.js the only officially supported SDK on their SaaS integrations. See Sitecore Cloud, Sanity, Contentful,....
- rk06 7mo ago
  Really the enterprise partner supports next, but not vanilla js sounds stupid? Honestly I expect them to prioritize nextjs and react given the popularity, but still be open to vanilla js. I checked sitecore cloud to have special integration for nextjs and reactjs. But it also support vanilla js as well. Are there really anyone who is exclusive to nextjs?
  - pjmlp 7mo ago
    Vanilla JS is "supported" if you write the missing parts, e.g. layout service, visual editing integration,... In many places they will say it is supported, but when you look into the details only React/Next.js work out of the box without additional work. A bit like you can deploy Next.js on Vercel, or do it yourself somewhere else.
rvcdbn 7mo ago
maybe of interest: https://github.com/cloudflare/vinext https://github.com/cloudflare/vinext (haven't tried it myself)
- vijaybritto 7mo ago
  It's not a good piece of software. Breaks in many places
  - littlecranky67 7mo ago
    "Read the announcement: How we rebuilt Next.js with AI in one week".
  - rozenmd 7mo ago
    that makes sense, it's not 1.0 yet
CalRobert 7mo ago
Got back in to react after a few years’ hiatus and I struggle to even understand what the point of Next is. Bizarrely the official docs even reference Next. Are people using react for non-SPA’s? Why?
- pjmlp 7mo ago
  The point is JavaScript developers rediscovering PHP, Spring MVC, ASP.NET MVC, Rails,..... And to sell Vercel on top.
- codetantra 7mo ago
  After Tanstack Start, Next.js seems even less intuitive. While it remains a viable option due to its established momentum, it feels quite alien to backend devs, esp with its unconventional defaults.
  - CalRobert 7mo ago
    It feels like Wordpress inasmuch as it’s shoving a tool in places that don’t make sense. React is great for SPAs but if I wanted pre-rendered static content I’d use a different tool.
    - patates 7mo ago
      I had had a client cancel a job when they heard it's not going to use Wordpress. It was going to be a dashboard showing statistics (air quality, room bookings etc.) from their facility.
    - davidodio 7mo ago
      why? jsx is a great language for templating, the ui being a function of state is an incredible model. i am not a huge nextjs fan but React, mdx and friends are great for pre-rendered static content
      - skydhash 7mo ago
        Isn’t all templates language that way (blade, jade,…)? The main selling point of JSX is being a DSL for React, which present a functional model instead of the imperative paradigm of the DOM API.
gherkinnn 7mo ago
It's the Vercel way to first run broken previews for several years. Next started with Turbopack alpha as a Webpack alternative in Next 13 (October 2022) and finally marked Turbopack as stable and default in Next 16 (October 2025). They also ran sketchy benchmarks against Vite back in 2022 [0]. Next's caching has a terrible history [1], it is demonstrably slow [2] (HN discussion [3]), RSCs had glaring security holes [4], the app router continues to confuse and relied on preview tech for years, and hosting Next outside of Vercel requires a special adapter [5]. Choosing Next.js is a liability. 0 - https://github.com/yyx990803/vite-vs-next-turbo-hmr/discussions/8 https://github.com/yyx990803/vite-vs-next-turbo-hmr/discussi... 1 - https://nextjs.org/blog/our-journey-with-caching https://nextjs.org/blog/our-journey-with-caching 2 - https://martijnhols.nl/blog/how-much-traffic-can-a-pre-rendered-nextjs-site-handle https://martijnhols.nl/blog/how-much-traffic-can-a-pre-rende... 3 - https://news.ycombinator.com/item?id=43277148 https://news.ycombinator.com/item?id=43277148 4 - https://nextjs.org/blog/CVE-2025-66478 https://nextjs.org/blog/CVE-2025-66478 5 - https://opennext.js.org/ https://opennext.js.org/
- ssijak 7mo ago
  Next took a very bad turn and double downed on it. Coupled with years of terrible bugs its beyond repair for me unless they rewind a bunch of core changes they did. There are several much better options right now. My favourite is Tanstack Start. No magice, great DX
  - adamgoodapp 7mo ago
    +1 for Tanstack start. I just setup a new project with it and like the whole ecosystem. Only slight disadvantage is most third party documentation and automatic setup with packages aren't setup for Tanstack Start yet.
- littlecranky67 7mo ago
  Any suggestions to replace NextJS when you only use static export (no SSR)?
  - 7mo ago
rk06 7mo ago
Vercel owns nuxt and sveltekit, so they do benefit. only nextjs suffers from not being on vite.

pjmlp 7mo ago

They have the enterprise partners that make Next.js the only officially supported SDK on their SaaS integrations. See Sitecore Cloud, Sanity, Contentful,....

rk06 7mo ago
Really the enterprise partner supports next, but not vanilla js sounds stupid? Honestly I expect them to prioritize nextjs and react given the popularity, but still be open to vanilla js. I checked sitecore cloud to have special integration for nextjs and reactjs. But it also support vanilla js as well. Are there really anyone who is exclusive to nextjs?
- pjmlp 7mo ago
  Vanilla JS is "supported" if you write the missing parts, e.g. layout service, visual editing integration,... In many places they will say it is supported, but when you look into the details only React/Next.js work out of the box without additional work. A bit like you can deploy Next.js on Vercel, or do it yourself somewhere else.

rvcdbn 7mo ago

maybe of interest: https://github.com/cloudflare/vinext https://github.com/cloudflare/vinext (haven't tried it myself)

vijaybritto 7mo ago
It's not a good piece of software. Breaks in many places
- littlecranky67 7mo ago
  "Read the announcement: How we rebuilt Next.js with AI in one week".
- rozenmd 7mo ago
  that makes sense, it's not 1.0 yet

CalRobert 7mo ago

Got back in to react after a few years’ hiatus and I struggle to even understand what the point of Next is. Bizarrely the official docs even reference Next. Are people using react for non-SPA’s? Why?

pjmlp 7mo ago
The point is JavaScript developers rediscovering PHP, Spring MVC, ASP.NET MVC, Rails,..... And to sell Vercel on top.
codetantra 7mo ago
After Tanstack Start, Next.js seems even less intuitive. While it remains a viable option due to its established momentum, it feels quite alien to backend devs, esp with its unconventional defaults.
- CalRobert 7mo ago
  It feels like Wordpress inasmuch as it’s shoving a tool in places that don’t make sense. React is great for SPAs but if I wanted pre-rendered static content I’d use a different tool.
  - patates 7mo ago
    I had had a client cancel a job when they heard it's not going to use Wordpress. It was going to be a dashboard showing statistics (air quality, room bookings etc.) from their facility.
  - davidodio 7mo ago
    why? jsx is a great language for templating, the ui being a function of state is an incredible model. i am not a huge nextjs fan but React, mdx and friends are great for pre-rendered static content
    - skydhash 7mo ago
      Isn’t all templates language that way (blade, jade,…)? The main selling point of JSX is being a DSL for React, which present a functional model instead of the imperative paradigm of the DOM API.

gherkinnn 7mo ago

It's the Vercel way to first run broken previews for several years. Next started with Turbopack alpha as a Webpack alternative in Next 13 (October 2022) and finally marked Turbopack as stable and default in Next 16 (October 2025). They also ran sketchy benchmarks against Vite back in 2022 [0]. Next's caching has a terrible history [1], it is demonstrably slow [2] (HN discussion [3]), RSCs had glaring security holes [4], the app router continues to confuse and relied on preview tech for years, and hosting Next outside of Vercel requires a special adapter [5]. Choosing Next.js is a liability. 0 - https://github.com/yyx990803/vite-vs-next-turbo-hmr/discussions/8 https://github.com/yyx990803/vite-vs-next-turbo-hmr/discussi... 1 - https://nextjs.org/blog/our-journey-with-caching https://nextjs.org/blog/our-journey-with-caching 2 - https://martijnhols.nl/blog/how-much-traffic-can-a-pre-rendered-nextjs-site-handle https://martijnhols.nl/blog/how-much-traffic-can-a-pre-rende... 3 - https://news.ycombinator.com/item?id=43277148 https://news.ycombinator.com/item?id=43277148 4 - https://nextjs.org/blog/CVE-2025-66478 https://nextjs.org/blog/CVE-2025-66478 5 - https://opennext.js.org/ https://opennext.js.org/

ssijak 7mo ago
Next took a very bad turn and double downed on it. Coupled with years of terrible bugs its beyond repair for me unless they rewind a bunch of core changes they did. There are several much better options right now. My favourite is Tanstack Start. No magice, great DX
- adamgoodapp 7mo ago
  +1 for Tanstack start. I just setup a new project with it and like the whole ecosystem. Only slight disadvantage is most third party documentation and automatic setup with packages aren't setup for Tanstack Start yet.
littlecranky67 7mo ago
Any suggestions to replace NextJS when you only use static export (no SSR)?
- 7mo ago

rk06 7mo ago

Vercel owns nuxt and sveltekit, so they do benefit. only nextjs suffers from not being on vite.