[rich_harris]

> I have no doubts they'll do the same with Nuxt, demanding they implement features that solely exist to pad out hosting costs while providing next to no actual benefits to end users and devs

has that happened with Svelte?

> they now have a monopoly over the most popular frontend meta frameworks (Next, Svelte/Kit, Nuxt, Astro)

this would be a surprise to the Astro team!

[sensanaty]

> this would be a surprise to the Astro team!

That's my bad, seems my memory failed me here!

[byyll]

> has that happened with Svelte?

Yes. There are features that have been deliberately kept on the platform level to force you to use the platform instead of implementing it on the framework level or guiding you through it with the docs.

https://svelte.dev/docs/kit/glossary#ISR

[rich_harris]

ISR _can't_ be implemented at a framework level without tying the framework to the platform. The fact that we instead chose to implement it via a platform-agnostic adapter API surely demonstrates the opposite of what you're implying

[0xblinq]

This would be true if you also provided an adapter-node, which would work on most traditional servers, and most non-serverless platforms.

The fact that you prioritize the vercel one and not the node native one proves what OP implies in my opinion.

[byyll]

It's platform agnostic but Vercel is the only one that supports it? At least that's in the docs I linked.