Yep, fairly heavy user here and it's basically fine for me, probably because I'm used to it. Simplicity works. Only thing I really wish for is a proper, first class, not-electron desktop app.
I also wish it had a native application. For my previous job I had to work on an 8GB Mac. Using Slack with 8 or so teams ate just short of 2GB. The solution was to start opening 1 or 2 teams in the browser at a time. One of the nice things about chat is being able to rapidly and immediately communicate, not being able to have my teams open all the time defeated that. I ended up running a ZNC server on AWS for persistent IRC connections to the Slack channels. This allowed me to have 8 teams open and be connected to a dozen IRC channels for under 2MB of RAM.
That hit me pretty acutely today when upgrading. Restarting slack took 15 seconds and pegged all 4 (8 logical!) cores. Why should a chat app ever do that?
I get that a billion dollars doesn't buy what it used to, but it really ought to buy native apps on at least all the major platforms.
Can you elaborate on what you find lacking/problematic in the Electron app? I find very little difference between it and any other proper desktop app. I'm on a 2013 MacBook Pro and I find it works very well.
Performance and resource usage mostly. It's a very, very good example of an Electron app, but it still shows its web flesh in various ways. Some reconnecting issues, incomplete page loads, UX weirdness (minor). Like I said, it's a great example, but that's like praising the beauty of an architectural masterpiece built on sand.
I completely gave up on Slack's desktop app and just use a browser. On the Mac, wrapping three teams in a Fluid custom browser saves me nearly a gigabyte of RAM...