3 ms·
> there's one huge one: It's slow. Really, really slow This is spot on. Its the same reason I hate Sharepoint - every implementation I've used was always incr
by nikau 6y ago
> there's one huge one: It's slow. Really, really slow
This is spot on.
Its the same reason I hate Sharepoint - every implementation I've used was always incredibly slow, so I would only ever use it when my arm was forced.
I miss old school "legacy" style apps that cached stuff so moving around the app is quick.
Even simple apps like slack suck these days as it always takes a few seconds to move around windows, why the hell can't it cache things? IRC clients in the 90s did about the same amount of stuff and they never lagged swapping servers or channels.
- redisman 6y agoI would guess because in slack the history can change when irc is basically a read only log. Slack has threads, edits, deletes and emojis etc. that will change the history so you can’t cache it
- nikau 6y agoI would prefer slack to update the channels in the background rather than on demand when I click a channel to view. This would probably be a bit more resource intensive, but I have network and CPU bandwidth to spare.