Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What does that have to do with Slack? If your computer has trouble playing high frame rate video it'll be the same on every application.


It's not just high framerate stuff, it's pervasive.

Folks used to post walls of dancing bananas in phpBB and my Pentium III could handle that without breaking a sweat.

The exact same wall of dancing bananas makes any modern CPU jump to ridiculous two-digit usage relative to the task at hand.

I was also chatting over IRC from a Palm Pilot which had something on the order of 1MB of RAM, connected over RS232 to a GPRS phone, and the current experience of chat performance is basically on par with that, which boggles the mind given that I now have ten thousand times the RAM, an internet connection that can't be saturated in practice, and latency largely bound by the speed of light.

Slack's requirements are completely ludicrous in regard of what it's set to achieve.

> it'll be the same on every application.

Except, it's not. Counterexamples of chat apps with reasonable to stellar performance abound over the last two decades.


Except that I can play a 4k 60fps 100Mbps bitrate HEVC video in vlc with 1/6th of the cpu usage slack needs to display a damned gif


I think you'll notice the CPU cannot play 4K 60fps in GIF format. Maybe the problem is literally the format itself, which is terrible. It's too bad something like MPEG or some of the animated PNG / JPEG / WEBM formats never took off for meme-y animated images.


I wonder if it would help if Slack converted gifs to MP4s in the background before displaying them, or if the perf problem is in the compositing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: