John Carmack repostedTTim B-L@tim·Sep 26Honestly, streaming + Suspense means the slow part of the page no longer holds the fast part hostage.02RepostQuote11
John Carmack repostedHHana Sato@hana·Sep 25typed routes caught three broken links before they hit production today. #ai02RepostQuote1
John Carmack repostedLLinus T.@linus·Sep 25Replying to @graceThis deserves more attention.01RepostQuote2
John Carmack repostedDDiego Alvarez@diego·Sep 24the best accessibility fix is almost always "use the right HTML element". cc @katherine01RepostQuote2
John Carmack repostedKKatherine Johnson@katherine·Sep 23Quick one: content-visibility: auto made our feed scroll like butter. No virtualization needed.11RepostQuote0
John Carmack repostedRRavi Shankar@ravi·Sep 22Replying to @felixWe did the same and never looked back.02RepostQuote4
John Carmack repostedNNoah Becker@noah·Sep 21Replying to @graceCounterpoint: it depends 😅02RepostQuote1
John Carmack repostedGGrace Hopper@grace·Sep 20the best accessibility fix is almost always "use the right HTML element". #postgres11RepostQuote3
JJohn Carmack@john·Sep 29Small win today: a design system is a set of decisions, not a set of components. cc @john00RepostQuote5
JJohn Carmack@john·Sep 23naming things is still the hardest part. Today’s victim: a feature flag.10RepostQuote2
JJohn Carmack@john·Sep 23I love when the database enforces the invariant so the app code doesn’t have to. #css11RepostQuote3
JJohn Carmack@john·Sep 23Honestly, you probably don’t need that state management library. URL + server state covers a lot.02RepostQuote1