Svelte is financed by vercel, so who knows if sveltekit drifts in the same direction.

Imustaskforhelp 5 days ago | parent | next [-]

Yes I know but the way I see sveltekit is that there are adapters for cloudflare etc. and I doubt how sveltekit can drift into such direction without immense blacklash

I don't know much about the nextjs and whether it was open like sveltekit currently is.

To me, nextjs (I think) was always meant to favour vercel but sveltekit has a rich history of managing multiple adapters.

Now, that being said there are still some chances of a rugpull that might happen but if that ever happens, I am staying on the last sveltekit that worked with cf and other cloud providers.

▲

benmccann 5 days ago | parent | prev [-]

Only 3/40 Svelte maintainers work at Vercel and they mainly finance work on Svelte core. SvelteKit day-to-day is primarily maintained by folks outside Vercel

▲

gigatree 5 days ago | parent [-]

A little disingenuous to say “only 3/40” maintainers. Which 3? And how percentage of the total work hours invested per month do those 3 represent?

	▲	benmccann 5 days ago \| parent [-]
		The number 3, 4, and 5 contributors to SvelteKit in the past year work at Vercel: https://github.com/sveltejs/kit/graphs/contributors?from=8%2... Rich and Simon are incredibly important, but they're in it for Svelte and the community more so than a paycheck from Vercel. Tee has been doing most of the maintenance on SvelteKit currently funded by community donations. And this isn't counting other infrastructure like vite-plugin-svelte or the Svelte CLI which are entirely maintained by volunteers. I don't think Vercel funds a majority of the work on Svelte even if it might be close to it.