upvote
> Why it uses 400mb I have no idea.

Yes, this is an important detail as well.

Make a Slack clone, but have it perform way better than the original (less RAM, CPU usage), with a smaller storage footprint.

Also deliver on features faster than the original. And have those features be more tailored to what the users both want and need - and things they didn’t even know they needed as well.

This is, after all, what’s being promised, no?

reply
Slack would be a lot better if they supported clients via rest api or similar. I want to run it in a terminal window alongside IRC etc. I have no desire to put up with their ridiculous UI/UX decisions
reply
That's just the base footprint of an Electron-based app.

Which they do because it means they can ship the same thing in many places (actual browser, cross platform OS and mobile if they're lucky).

reply
But it's so unreasonably slow. It lacks basic features like syntax highlighting on ``` blocks. It's basically become a super expensive and painful to use while Discord continues to be a joy.

And the 'start a thread' nazis are just too much to bear. Prediction: they will add subthreads within 3 years.

reply
> And the 'start a thread' nazis

Social issues can't be solved by technical means. Just slightly incentivised in some direction (like discord's "this is the third reply, would you like a thread instead?")

But for the resource usage, ripcord https://cancel.fm/ripcord/ already proved you can have a capable client which is super light and fast if you care. This was made by a single person and in many ways is better than the official client.

reply
Prediction 2: companies will hire full-time Slack Cops whose whole job is shaming coworkers and talking about threads (the #1 Slack anti-feature).

Well, this was my prediction pre-easy-to-use LLMs, anyway.

reply
Electron?
reply