I use Discord daily and can't really call it slow and laggy, it feels adequate if anything.

Can't really comment on Slack and Teams - I've obviously used both, but haven't been a heavy user of Teams and never was in a large "corporation-wide" Slack instance. I have, however, been a heavy user and developer of a Slack competitor. Not surprisingly, it had a lot of problems, but most of them stemmed from a) clumsy handling of megabytes of chat logs, b) a codebase that grew organically out of a startup project and needed a major rewrite, c) misallocation of resources (for the longest time, everything Electron-related was handled by a single developer in a satellite office). In my opinion, we would have had the same performance issues and bugs if it had been developed in any other language. We actually had some Qt apps that we deprecated and rewrote in JS as part of the main client - there was no user-noticeable performance drop, but significantly fewer crashes.

▲

pdimitar 7 months ago | parent [-]

...OK?

It was already mentioned that people can do better apps with Electron than others. Not surprising.

My objection is that the possibility to make laggy and bad apps exists. It should not exist.

As for what problems a Slack competitor faces, well, I am not interested. That's the dev team's problem and not mine. I want a lagless Slack.

▲

DecoySalamander 7 months ago | parent [-]

> the possibility to make laggy and bad apps exists. It should not exist

I see. Then the only way forward is to stop all software development altogether and enjoy memories of apps that we used 20 years ago when we were much younger, and fantasies of apps that we could build with newly acquired wisdom, but will not.

	▲	pdimitar 7 months ago \| parent [-]
		Funny, still not what I said. Progress is way too slow and blindly follows local maximii. That's not OK. That's the part I am expressing displeasure with.