Interesting, in my case I'm using Capacitor (since I need bluetooth and it's not well supported across browsers), and I want the app to be able to work offline too for some features, so I don't really care about the bundle size (it ships with the native app) and I prefer SPA than MPA so I can build it once and ship it with the code

> when I built the first implementations and started measuring, something became clear: the issues I was seeing with Next.js weren’t specific to Next.js. They were fundamental to React’s architecture.

So here some obscure Next.js issues magically become fundamental React architecture issues. What are these? Skill issues?

Great post. Im moderately annoyed that on Safari mobile it has an incorrect and super annoying horizontal scroll.

Excellent work, I love experiments like these. Unsurprisingly the site is also lightning fast to load.

> 40ms round-trip time

In that case how can you possibly get 35ms FCP? Am I missing something?

Comparing something like next.js to other frameworks doesn’t make much sense anymore given that most webdevs choose DX and easy deployment above anything else. Vercel’s growth is proof of that.

> This isn’t just an inconvenience. It’s technofeudalism.

> This isn’t a todo list with hardcoded arrays. It’s a real app with database persistence (appears twice)

this article was written by ChatGPT. I'm tired

Any reason the url is '10-kanban-boards'? I noticed this when I copied the url to share.

Reference to SpeedCurve, they have a skip link on their home page yet nowhere id="main" was found.