If you're ever feeling down about your code, keep your chin up: I just noticed the AWS SDK has had this for six years 😬
(you can't compare arrays like this in JS)
I've made a PR to optimize some of that work. It currently creates 1745 ReadableStreams per request unnecessarily 😬
This fix eliminates that and you get a 10-38% perf boost (Deno users get the most!)
github.com/vercel/next.js…
What makes Next.js slow? In cases like @theo's benchmark, it's because it's creating multiple React streams, parsing and rendering to JSON and HTML, reading the whole body along the way and doubling the payload. Next.js = 220ms, plain React streams the same thing in 27ms
One of the biggest engineering costs you can reduce is developer-thumb-twiddling. Brought our frontend CI time down from 8 mins to 25 secs by parallelizing on AWS Lambda (@lamb_ci). Each Lambda tests every nth file (testing/formatting/linting 3k files over 13 sites).
