Things I learned from 5 years at Vercel

Re:Things I learned from 5 years at Vercel by sunaookami on Friday July 11, 2025 @06:27PM (#44537402)

Next.js has many weird bugs and things that just... don't work and when you hit these edge cases and a >5 year old open GitHub issue you know you will spend the next two weeks searching for another way or just abandoning it because it doesn't work. Got burned out hard by Next.js while rewriting a very old project - it worked in the end and I was proud of it but just using something... simpler would've been better. Deploying Next.js outside Vercel is hell, too...

Also tried SvelteKit (with Svelte 4) which was quiet nice but it completely misbehave in production with a lot of corner-case bugs that were not reproducable in development and I abandoned it for good. Didn't the creator of Svelte even joined Vercel? They seem to want to "unite" all the JS frameworks "under one roof" which I find a bit... disturbing?

[ Parent | on HN ]

Re:Things I learned from 5 years at Vercel by ashwinsundar on Friday July 11, 2025 @06:49PM (#44537571)

Nuxt joined Vercel earlier this week too - https://vercel.com/blog/nuxtlabs-joins-vercel

[ Parent | on HN ]

Re:Things I learned from 5 years at Vercel by harrisi on Saturday July 12, 2025 @12:53AM (#44539396)

I believe all the core contributors to Svelte and SvelteKit are employed by Vercel.

[ Parent | on HN ]

Re:Things I learned from 5 years at Vercel by rich_harris on Monday July 14, 2025 @09:26AM (#44559953)

Three of us are employed by Vercel, and we're probably responsible for over 50% of commits. The core team is much larger than just us though

[ Parent | on HN ]