In an effort to save 1.5ms of scrolling jitter, I have rebuilt our media playback system.
The things you have to do to play nice with mobile hardware and 120hz screens.
Discussion
My pixel 8 pro thanks you for your service 🫡
Can't zap you Vitor 🤔
I can't zap myself either. What's going on nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcprdmhxue69uhkummnw3ez6vfwde3x7tnpdenkzmnf9e3k75xqss4?
Hey sorry, didn't notice that! What's your setup, how do you host your node?
As for now it works fine...
1.5ms doesn't cause jitter when you paint the frame every 8ms. What computation budget do you have per frame? (How many ms?)
1.5ms of 8ms is a lot just to create a video player. The app has to render everything else in that time. Each clickable area of a post is about 0.5ms. So, just the reaction buttons/row alone is about 4ms. The author picture, name and top line in the post is another 2ms. The text takes another 2 to 6ms depending on how big and how many clickable elements it has.
Congratulations, 🎉🙌