Ripcord is great and I use it for Discord and Slack, but it is far from feature complete. Important to note that Ripcord is developed by one person. Some major things that are lacking:
* No search (Slack/Discord)
* No huddles in Slack
* Thread support in Discord
For these reasons, I typically navigate to Discord/Slack in the browser when I need access to those features. Not ideal, but the snappiness of Ripcord over the slow bloat of Slack/Discord make it worth it to me.
Ripcord has had search support in Slack for a while, it's under the Workspace menu. Otherwise, yeah. It's unfortunate to have to open the browser to do some of this stuff but the day-to-day experience of using it is great.
Agree to disagree. Selecting a channel in Slack takes like 300ms for me almost every time. There seems to be an inherent UI lag with Slack and Discord. Ripcord, on the other hand, is instantaneous.
Wholeheartedly agree that that's not acceptable performance, but blaming electron, which runs on chromium which is famously fast (despite its other issues) seems misguided.
To me it sounds like an artifact of architectural choices, eg by polling before rendering to avoid flicker, lack of client side caching, or possibly just bloat. Companies won't stop their poor software practices even if they switched to native.
The post I responded to mentioned the Electron; I was talking about the client performance in the browser, but I've had similar experiences with the Electron clients for Discord and Slack.
I don't doubt you can make a performant snappy chat GUI with Electron/web tech, but more often than not, in my experience, Qt apps (like Ripcord) perform much better and are less RAM hungry.
* No search (Slack/Discord)
* No huddles in Slack
* Thread support in Discord
For these reasons, I typically navigate to Discord/Slack in the browser when I need access to those features. Not ideal, but the snappiness of Ripcord over the slow bloat of Slack/Discord make it worth it to me.