3 ms·
Their app has compicated and clumsy UI that looks like it was made by programmers rather than by a designer and very high memory usage. Here is an example of me
by codedokode 8y ago
Their app has compicated and clumsy UI that looks like it was made by programmers rather than by a designer and very high memory usage. Here is an example of memory usage from a small team with little volume of messages, reported by smem on Linux:
- 5 processes
- over 850M in swap
- over 310M PSS (Proportional set size which is the only indicator showing true memory usage)
This is over 1 Gb total. Despite high memory usage, they don't provide 32-bit version for Linux. It is surprising how such product can become profitable.
- erdaniels 8y agoThat’s not surprising at all. Sure it would be great if it had a light footprint but it’s usability far outweighs that.
- Kovah 8y agoProbably because those people who use the app most do not care about memory usage. Everytime somebody complains about how resource-hungry Slack is, it usually comes from a developer. I rarely see project managers or designers or even clients complain. And, looking at the company I work for, the developers channel is the one with the lowest usage. This is why Slack became successful: it works for the people who need it most, not because it is very resource-efficient or well coded.