Re:We Fell Out of Love with Next.js and Back in Love with Ru...
by jakubmazanec on Sunday May 04, 2025 @11:51AM
(#43887424)
True, the 1s+ delays (both on mobile and desktop!) and no spinners is a very annoying UX.
I've been saying this forever and this is a great reminder for those React-hating folks here on HN: usually it's the developer's fault his web is slow, not the framework's.
Re:We Fell Out of Love with Next.js and Back in Love with Ru...
by yellow_lead on Sunday May 04, 2025 @11:39AM
(#43887346)
I don't have this delay personally. Probably the page speed metric is more accurate because it smooths out anecdotes like ours.
Re:We Fell Out of Love with Next.js and Back in Love with Ru...
by petetnt on Sunday May 04, 2025 @11:47AM
(#43887401)
Page speed metric shows 5.2s for the first contentful paint for the mobile home page too: https://pagespeed.web.dev/analysis/https-hardcover-app-feed-...
Re:We Fell Out of Love with Next.js and Back in Love with Ru...
by yellow_lead on Sunday May 04, 2025 @12:29PM
(#43887655)
I didn't realize you were trying mobile initially. When I tried mobile, it also seems incredibly slow. My desktop didn't have this issue (when going from explore page to home). Everything seems a lot slower on mobile.
Re:We Fell Out of Love with Next.js and Back in Love with Ru...
by dyogenez on Sunday May 04, 2025 @12:54PM
(#43887839)
That is one of the slower pages on the entire app. I'd like to move that one to use an InertiaRails.deferred setup, so it loads instantly with a loading spinner - like you'd see with Suspense + RSC. (Hardcover founder here)
You cannot just blindly trust the page speed metric but it should be impossible to miss things like this when you are actually using the site. Compare the experience to something like GoodReads that's using plain old SSR and you'll immediately notice the difference.