> Like I'm sorry but it's essentially IRC.
It's irc with emojis, 2mb animated gifvs, embedded hd video and other complex content rendering. Of course it's using as much ram and cpu as a browser.
It's irc with emojis, 2mb animated gifvs, embedded hd video and other complex content rendering. Of course it's using as much ram and cpu as a browser.
It's why you use Slack, rather than why people use Slack. I'm sure you could make do without the emojis, GIFs, and videos, but the market says people seem to think otherwise.
(Ok, I remember HipChat didn't have gifs but there was a lot else wrong with HipChat)
Slack is nicer than IRC to use. Nobody here is debating that. Slack solves a heap of problems with IRC.
My only point of contention is that there is zero argument for it using the resources it does. None of the mentioned solutions require any more resources than IRC consumes.
We just have a big heaping pile of electron nobody wants to acknowledge as the source of the problem.
Yes it often makes sense to produce inefficient code for many business reasons (development speed, users don't care, easier platform to deploy to, etc).
However what Slack does would be nowhere near taxing for a modern computer if it were to be done remotely efficiently.