Why it uses 400mb I have no idea.
Why it uses 400mb I have no idea.
(And of course, way back then there was an official IRC interface, too)
My comment was a response to
> Slack would be a lot better if they supported clients via rest api or similar.
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?
If it can’t produce an executable that minimizes RAM and storage for something like Slack, are we supposed to believe it can for something more traditionally power-hungry (browsers), or storage hungry (Call of Duty, iPhone apps)?
Shouldn’t AI be on the forefront for reducing resource usage in general (not just digital resources), or is just a giant exercise in induced demand / Braess’ paradox?
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).
And the 'start a thread' nazis are just too much to bear. Prediction: they will add subthreads within 3 years.
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.
Well, this was my prediction pre-easy-to-use LLMs, anyway.
Along with syntax highlighting.