5 ms·
> A lot of Slack's high (background) CPU usage is caused by GIFs, in my experience. Holy fuck, can you imagine the supercomputers that were required to displa
by notalaser 10y ago
> A lot of Slack's high (background) CPU usage is caused by GIFs, in my experience.
Holy fuck, can you imagine the supercomputers that were required to display Geocities websites in the 1990s?
- turrini 10y agoThat was just gold
- magicalist 10y ago48x48 gifs with four frames of animation?
- notalaser 10y agoThe GIFs were significantly more complex than the single emoji that the parent comment mentioned. Actually, I think even a four-frame 48x48 gif is more complex than that "single animated parrot emoji" :-).
- Asooka 10y agoWell, back then we didn't have a composited desktop, so when the browser was out of view, no drawing was taking place. I kind of wish we would still have the option of programs just drawing directly to the screen rather than caching everything in private back buffers, but still use modern graphics techniques. I have a hunch that would actually be faster, since cpus have severely outpaced memory.