Thread

1. smy20011 · 1790195297 · focus · HN ↗

   The way Claude did it is fight entropy with entropy.

   "Add a static composer into the HTML" <- This seems like something can be done with SSR?

   "For faster navigations, we kept the composer mounted between conversations" <- Your SPA should cache this between pages, why fetching it every time? Or you need better routing for your react components.

   "cheap first-character check before the regex" <- Should we cache compiled Regex instead?

   I think even 1.3 sec to load the front page is unacceptable. Something need to be reworked from basics (SSR, chunk-based rendering) to solve the problem. Focusing on invidual benchmarks may miss the opportunity.

   1. crooked-v · 1790201452 · focus · HN ↗

      Even Next.js, for all that people are unhappy about its quirks, complexity, and random undocumented behavior and bugs (God help you if you ever want to try and actually use parallel routes as documented), can do all of this SPA stuff out of the box. Use `<Suspense>` appropriately on data loading, and everything static (including e.g. purely input-output components like editors) will load once and be re-used forever, and your Suspense-wrapped items will show a loading placeholder and only re-load when you intentionally re-trigger the data loading (which you can push down all the way to the level of individual buttons if you want).

Unofficial Hacker News client; not affiliated with Y Combinator.