I've found (and locally fixed) an annoying performance bug on @X web! TLDR: go to a post with a lot of replies, and scroll up and down - notice it's laggy? There's a component that calculates the scroll parent, and then removes the scroll listener when unmounting. But it seems we don't even have a scroll listener most of the time, so we can avoid the heavy _getScrollParent function by wrapping it in a conditional This removes seconds of forced reflow and lag for me Would love to get it fixed! 🙏🏻 @X @engineering @elonmusk @nikitabier

how I feel when running fast

Berlin marathon tomorrow! No time goal, just going to enjoy it and play around See you on the other side 🫡

I feel like this has become worse We're now at the stage where people are micro-optimizing specific tasks and orchestrations for different effort levels I'm still confused about what to use

TIL

"optimizing the homelab" arc 🚀🚀🚀

Cutting the performance grass ✂️

i love loose goose models

trying to get nerfed AI models to do security vulnerability research

Constantly running into them 🫠

I fucking love this gif

Insane graph 😱

Let's fucking go

hi Berlin

"This is too slow, make it faster" 👏🏻

wow opus 5.5, what a great model

I'm on a long-distance train with slow WiFi (no Starlink) and it's literally better to use my agent to search the web than to use a browser, thanks to every site needing to download 492576 MB of JS just to show a login page

don't be a doomer, be a bloomer

make your application so fast it could be served by 1 raspberry pi

Spend your evenings improving performance 🚀