I really appreciated that the tone of the article is about what can be improved, rather than dunking on the competition.
That's what everything is about!
PS: It's awesome to see improvements on the OpenNext implementation, that other providers can also reuse
This is great PR. Well done to whoever orchestrated that post.
This is why we need competition and independent benchmarks.
This shames poor performing product/service into action.
Good job on taking the L gracefully and doing something constructive about it
My take from this article is that SvelteKit is crazy fast and Next.js is a snail
Speaking of `JSON` functions that can have drastic performance differences, V8 blog[0] recently had a post about improving `JSON.stringify` performance when you don't pass a `replacer` function. Some of the most used functions with performance pitfalls that are easy to trip into.
0: https://v8.dev/blog/json-stringify
I loved this! Good writeup and very mature response to lots of criticism they took online prior.
nextjs being 4 times slower latency wise than plain react or even vanilla js is pretty funny
The benchmark cases are not comparable to each other. Each does totally different work. They are only meant to compare hosting providers.
Correction: The author of the SvelteKit benchmark says it is designed to do the same work as the Next.js one: https://x.com/bmdavis419/status/1978242304432325041
But the "vanilla" benchmark generates some 3x as much HTML and the react one generates half, so they aren't comparable.
nextjs is spring of the web, it optimizes productivity rather than app speed.
and whether you are more productive with it or not is completely up to you.
cf has to hire people with obsession not benchwarmers that only activate when someone yells at them because of a twitter argument. there i said it.
vercel only exists because cf got lazy.
huge fan of CF, and if cloudflare had the attention to details that vercel has, there would be no vercel. fullstop.
CFs docs, repos, video content but also code samples, sdks (lol all the mcp stuff) usually is subpar to vercel's.
its really annoying that nextjs has to be forked and/or patched to work on cloudflare.
CF isn't lazy at all. Their docs often aren't that great but it's because they seem to be prioritizing launching new products and features
Grab the popcorn, the Vercel v Cloudflare drama unfolds