![how many people use slack desktop app how many people use slack desktop app](https://www.nordtheme.com/static/a920f1178548bb16b095faddfc526a52/a3403/overview.png)
#How many people use slack desktop app software
Unfortunately, this is just the way modern team software engineering goes. You're going to do something less than ideally efficient. You don't have context of the really nitty gritty details someone who wrote the original framework thought about. (unlike traditional, slow, non-agile development where a person owns a certain module/component and is the expert and works on it for years) When you move to a new feature, you need to pick up on all the details of how it works previously, and you build your stuff on top of it. And then in modern software dev shops, you typically put devs on different features on a weekly basis. Slack has a collection of apps and integrations that makes it much more powerful and useful than personal messaging apps. It has many great features that make it a very useful tool to have in a workplace. 20 people doing that, memory usage just grew by 2gb. Slack is the market leader in collaboration tools and has been that way for some time now. If your feature grows memory usage by 100mb, it's not a big deal. When you have a whole team working on a huge piece of software, each person is working on one part of it at a time. When one developer is working on a program, the person tends to be able to keep track of program flow, memory usage in their head and know when things are about to go out of bound, memory shoots up, etc. I think "team software engineering" plays a big part of this, if not even the main reason. I know most of this thread has been about making fun of Slack, but I wanted to write a somewhat serious response to this. Welcome to the wonderful world of JS/CSS/HTML5 apps. Even excluding these issues, and allowing for several canvas layers at 1366 x 768 x 32 bits per pixel, double-buffered, and the thing still seems to consume quite a bit of RAM. Some of this is down to the idiotic way the Web Audio API handles compressed audio, but with Asteroids I have to pre-render a lot of images because canvas 2D performance isn't that great with drawing primitives. Same issue with my version of Asteroids too. Uses 284MB, for a version of a vector arcade game from 1980. Users can add emoji buttons to their messages, on which other users can then click to express their reactions to messages. Content, including files, conversations, and people, is all searchable within Slack. Same with any app that's basically a browser app: memory usage is out of control relative to what the application does.Ĭase in point: (disclaimer: I wrote this). Slack offers many IRC-style features, including persistent chat rooms (channels) organized by topic, private groups, and direct messaging. For the love of Pete! It's a frigging IM client: 800MB is absolutely not a reasonable amount of memory for it to be consuming, and I don't care how long your message history is.Ī big part of why this occurs is Electron.