9 ms·

Yeah I don't get why so many other commenters seem to think a direct listing means the company's all of a sudden about to die or its product is all of a sudden

Yeah I don't get why so many other commenters seem to think a direct listing means the company's all of a sudden about to die or its product is all of a sudden going to turn to crap. If this is the best way to achieve liquidity, that sounds good for them.

lugg 8y ago
Their product kind of did turn to crap. 30% cpu at idle with 5 accounts. 50% if I enable emojis. Like I'm sorry but it's essentially IRC. There is zero excuse for being that much of a hog. You can blame it on electron if you like (I do) but it doesn't change anything for the end user.
- adamnemecek 8y ago
  [deleted]
  - sbov 8y ago
    They weren't saying its just IRC so it isn't a viable business model. They're saying its just IRC so it shouldn't be a CPU hog. Your link is not really relevant here because it talks of business viability not program performance.
- bduerst 8y ago
  Apparently they've fixed a lot of the CPU issues, it's just still in Beta: https://medium.com/@matt.at.ably/wheres-all-my-cpu-and-memory-gone-the-answer-slack-9e5c39207cab https://medium.com/@matt.at.ably/wheres-all-my-cpu-and-memor...
  - deleted 8y ago
    [deleted]
  - sbov 8y ago
    That was written in July 27 2017. I doubt its still in Beta.
- smileysteve 8y ago
  > Like I'm sorry but it's essentially IRC. It's irc with emojis, 2mb animated gifvs, embedded hd video and other complex content rendering. Of course it's using as much ram and cpu as a browser.
  - obl 8y ago
    Of course ? Yes it often makes sense to produce inefficient code for many business reasons (development speed, users don't care, easier platform to deploy to, etc). However what Slack does would be nowhere near taxing for a modern computer if it were to be done remotely efficiently.
  - jen20 8y ago
    Which of course misses the point of why people use Slack over IRC: history without screwing about. I could make do without the emojis, GIFs, video or other content rendering if IRC had history without the need for a constant connection.
    - yzmtf2008 8y ago
      >Which of course misses the point of why people use Slack over IRC: history without screwing about. It's why you use Slack, rather than why people use Slack. I'm sure you could make do without the emojis, GIFs, and videos, but the market says people seem to think otherwise.
      - therein 8y ago
        To be fair, why he uses Slack is likely due to his employer using Slack.
        quickthrower2 8y ago
        And the reason his employer uses it is to ensure everyone can interrupt everyone and give each other more work.
      - lmm 8y ago
- mr_custard 8y ago
  Also adding: Slack Helper eventually goes into a death spiral and uses almost all of the CPU under macOS. I have to force quit it every other day or so. Slack seems to have been doing that for roughly 2 years. Slightly mitigating data point: Other Electron apps do this too.
  - deleted 8y ago
    [deleted]
  - markmark 8y ago
    I have never had this happen on my mac running Slack.
    - mr_custard 8y ago
      Perhaps it's down to hardware differences then, assuming that you've got a newish machine. This is a fairly old MacBook Pro which will be replaced soon. Hard to say what the cause is, but I don't have any issues with other non-Electron apps.
- tptacek 8y ago
  Are you new to Slack? People have been joking about the resource demands of the Slack desktop client for years. If anything, that situation is actually improving.
- Wintereise 8y ago
  Anecdotal, but with 5 workspaces joined, Slack idles between 0-2% while on the foreground for me. This is a fairly modest i7 3770k based system. Their work on reigning in runaway CPU usage truly seems to have paid off.
  - chx 8y ago
    Calling a 3770k modest is a stretch but I have a mobile dual core here (OK, it's a Kaby Lake but still) and also seeing 0% in Task Manager.
    - semi-extrinsic 8y ago
      If having a six-year-old CPU isn't considered modest, it really says something about the lack of progress in the CPU space.
      - chx 8y ago
        We discussed this recently: from Sandy Bridge to Kaby Lake , IPC grew 20%, power consumption dropped brutally. And by Kaby Lake progress has completely stalled due to Intel's inability to switch to 10nm allowing AMD to catch up.
- deleted 8y ago
  [deleted]

lugg 8y ago

Their product kind of did turn to crap. 30% cpu at idle with 5 accounts. 50% if I enable emojis. Like I'm sorry but it's essentially IRC. There is zero excuse for being that much of a hog. You can blame it on electron if you like (I do) but it doesn't change anything for the end user.

adamnemecek 8y ago
[deleted]
- sbov 8y ago
  They weren't saying its just IRC so it isn't a viable business model. They're saying its just IRC so it shouldn't be a CPU hog. Your link is not really relevant here because it talks of business viability not program performance.
bduerst 8y ago
Apparently they've fixed a lot of the CPU issues, it's just still in Beta: https://medium.com/@matt.at.ably/wheres-all-my-cpu-and-memory-gone-the-answer-slack-9e5c39207cab https://medium.com/@matt.at.ably/wheres-all-my-cpu-and-memor...
- deleted 8y ago
  [deleted]
- sbov 8y ago
  That was written in July 27 2017. I doubt its still in Beta.
smileysteve 8y ago
> Like I'm sorry but it's essentially IRC. It's irc with emojis, 2mb animated gifvs, embedded hd video and other complex content rendering. Of course it's using as much ram and cpu as a browser.
- obl 8y ago
  Of course ? Yes it often makes sense to produce inefficient code for many business reasons (development speed, users don't care, easier platform to deploy to, etc). However what Slack does would be nowhere near taxing for a modern computer if it were to be done remotely efficiently.
- jen20 8y ago
  Which of course misses the point of why people use Slack over IRC: history without screwing about. I could make do without the emojis, GIFs, video or other content rendering if IRC had history without the need for a constant connection.
  - yzmtf2008 8y ago
    >Which of course misses the point of why people use Slack over IRC: history without screwing about. It's why you use Slack, rather than why people use Slack. I'm sure you could make do without the emojis, GIFs, and videos, but the market says people seem to think otherwise.
    - therein 8y ago
      To be fair, why he uses Slack is likely due to his employer using Slack.
      - quickthrower2 8y ago
        And the reason his employer uses it is to ensure everyone can interrupt everyone and give each other more work.
    - lmm 8y ago
mr_custard 8y ago
Also adding: Slack Helper eventually goes into a death spiral and uses almost all of the CPU under macOS. I have to force quit it every other day or so. Slack seems to have been doing that for roughly 2 years. Slightly mitigating data point: Other Electron apps do this too.
- deleted 8y ago
  [deleted]
- markmark 8y ago
  I have never had this happen on my mac running Slack.
  - mr_custard 8y ago
    Perhaps it's down to hardware differences then, assuming that you've got a newish machine. This is a fairly old MacBook Pro which will be replaced soon. Hard to say what the cause is, but I don't have any issues with other non-Electron apps.
tptacek 8y ago
Are you new to Slack? People have been joking about the resource demands of the Slack desktop client for years. If anything, that situation is actually improving.
Wintereise 8y ago
Anecdotal, but with 5 workspaces joined, Slack idles between 0-2% while on the foreground for me. This is a fairly modest i7 3770k based system. Their work on reigning in runaway CPU usage truly seems to have paid off.
- chx 8y ago
  Calling a 3770k modest is a stretch but I have a mobile dual core here (OK, it's a Kaby Lake but still) and also seeing 0% in Task Manager.
  - semi-extrinsic 8y ago
    If having a six-year-old CPU isn't considered modest, it really says something about the lack of progress in the CPU space.
    - chx 8y ago
      We discussed this recently: from Sandy Bridge to Kaby Lake , IPC grew 20%, power consumption dropped brutally. And by Kaby Lake progress has completely stalled due to Intel's inability to switch to 10nm allowing AMD to catch up.
deleted 8y ago
[deleted]