Live data from Hacker News

Migrating Slack's Desktop App to BrowserView

slack.engineering

211–214 of 214 posts

Re: Migrating Slack's Desktop App to BrowserView

#211
post #12

Earlier quoted context omitted.

I'll second this and note that Telegram, an app actually written in native code, is currently using ~500MB on my machine right now. I hate to be the one to say it (mostly because I just don't care about the ensuing argument), but I think most people who decry Electron/et al don't actually have that great of an understanding of how memory works. I say this as a guy currently sitting here writing an iOS/macOS app in Ob…

I'd challenge that. I have been using the Telegram native client on Windows since ~3 years and I don't remember having it ever going beyond 100 MB usage of RAM or ANY spikes in CPU usage (usually ~60 MB and 0% CPU). It usually sits there, quietly. Maybe its using more RAM when I take a call with it, but since its going back to normal after I finish (or it's always just low), it doesn't matter. I am using Slack since…

Aahhhh, I just saw this, sorry.

I'm happy to be wrong! I think one thing that sucks about these discussions is that everyone gets different results on their machines and it's difficult to pinpoint why memory usage might be so high - e.g, I have a slew of cryptocurrency chats open, so maybe Telegram is just doing that much more work or something?

Re: Migrating Slack's Desktop App to BrowserView

#212
post #26

Earlier quoted context omitted.

I was happy when we moved from the HipChat client that used several hundred MB of RAM over to Slack which is proving to at least be more svelt. I really don't want to go back to another RAM hog. It's not like my laptop is just brimming with extra RAM, and being a Mac of course the RAM isn't user upgradeable. My choice shouldn't be "be present in chat, or carry out work". Guess it's time to figure out IRC integration.

Use the Safari version of Slack. Push works and the Safari web content process is much smaller.

Except Safari keeps killing it because it's a CPU hog

Re: Migrating Slack's Desktop App to BrowserView

#213
post #187

Earlier quoted context omitted.

That's progress.

That's regression. Despite having vastly more memory than 20 years ago I'm not getting anything more done with it.

What OS were you using in 1997? I believe I was using Windows 95 then and was definitely getting a lot less done with it.

Re: Migrating Slack's Desktop App to BrowserView

#214

Earlier quoted context omitted.

No. That's actually almost never true. It certainly isn't what I meant.

Screen readers. System themes. Keyboard shortcuts. Text rendering. Visual effects on interaction. The list of things that go into making even a simple text box is surprisingly long, and varies a lot by operating system and over time. Browsers—well, Gecko and Edge; WebKit and Blink aren’t quite so good at it—tend to do things properly or to a remarkably high fidelity. They put enormous amounts of effort into getting i…

> If you care about your users and are not making a game, the sad truth is that drawing all the controls yourself is irresponsible.

I agree, but the solution is not going to web, but instead using the OS provided UI toolkits.

Post reply on HN