You know how you can render a 10,000-line diff without melting the browser? By focusing on simplicity. 🧵

After overhauling the React architecture of GitHub's "Files changed" tab, we dropped Interaction to Next Paint (INP) from ~450ms to ~100ms. 📉 React components cut from 8 to 2 per line 🔑 O(1) data access with JS Maps 🪟 Window virtualization for giant PRs

Here's how the engineers at GitHub made it happen. ⬇️ github.blog/engineering/ar…

@github Now just keep the site online

@github wow beautiful, now can you fix the back button never working?

As the new Official Payments Partner of the NFL, Amex is bringing Card Members closer to the action with special access and experiences at select events worldwide.

@github You broke scroll. Scrolling up on a diff is like rolling the dice, it throws you on a random position on the page. Please fix it!

@github 2 components per line... INP 100ms mid turn is nothing to brag about, really.

@github when the warning `... had recent pushes about 1 hour ago` shows up and push down the page it's really bad UX. find different way specially when there is weird things like the UI re-render twice for no reason

@github Just don't use React 🙃

@github Wow, 10fps

@github So my question is, why React?

@github How many 9s y’all got tho?