Putting aside the downsides and reasons not to use Electron, this statement is just false. They are not "constantly crashing." I currently use at least Figma, Insomnia, Slack, Spotify, and VS Code and these apps rarely crash, if ever.
So no, Slack (and other Electron apps) don't crash. But maybe they should. A hard crash (and automatic restart) is often better than the slow creeping insanity that seems to afflict Electron apps when their internal state gets out of sync with itself.
> (like not updating read/unread status of messages, waiting forever for content to load, not showing notifications, etc)
I have had all 3 of those with Thunderbird.
Is it possible to use the "windows" version of the Spotify electron client on Linux? That might make a difference since the Linux client is unsupported.
I'm not a fan of electron, heck, is go as far as to say I don't like it, but those statements are just unfair.
I run a bunch of electron apps on Linux every single day of the week for years now and I honestly can't say any of them have ever crashed.
Yes they may take up a bunch of RAM, but how many software engineers have less than about 16GB, and what's that RAM there for, if not too run my tools?
I can't say I've ever gotten over a few gigabytes of usage in a normal work day (not running any VMs for example). I don't use Chrome nor am I a tab-hoarder.
Whether I like electron itself or not, the told built in it seems to get the job I need done just fine. Who cares if it takes 3-4 second to open, once per day?
Dev environments that waste RAM keep people from learning how to program, and disproportionately affect anyone using cheap hand-me-down hardware.