Slack, renown for horrible app performance, should never be an example in any discussion about underlying architecture.
It seems poor performance is a core value at the company.
It seems poor performance is a core value at the company.
"handling"
Sending and receiving is something for a background thread to spend a fraction of a percent of a CPU core on.
The amount on-screen at any time is tiny, and should not take a significant amount of resources on a modern computer.
If it's rendering a thousand off-screen rich content messages, that's not impressive, that's it being coded badly.