4 ms·

Slack currently uses a separate webview for each team you're signed in to[1]. They're apparently working to optimize the app for those running multiple teams. P

Slack currently uses a separate webview for each team you're signed in to[1]. They're apparently working to optimize the app for those running multiple teams. People like to hate on Electron, but in this case Slack's implementation of multiple teams deserves more blame than the underlying stack. [1] https://slack.engineering/reducing-slacks-memory-footprint-4480fec7e8eb https://slack.engineering/reducing-slacks-memory-footprint-4... Quotes: >> This memory footprint increases as the user signs into more teams, as each team runs in its own webview. >> Each of these teams is running the full JavaScript web application and maintaining and updating the DOM tree as the state of the team changes. >> Work is underway to fix the underlying factors affecting client memory consumption >> Exploring running all teams in a shared context to eliminate the overhead of one webview per team.

shawnz 9y ago
> a separate webview for each team you're signed in to So then shouldn't it be the same penalty as having 11 pages of Slack open in Chrome? That seems like something not too extreme to me.
- developer2 9y ago
  I'm not certain of their use of the word "webview", nor exactly how multiple rendering windows work in Electron. In theory it should work the same as multiple tabs in a single Chromium instance. In any case, the Slack app is very heavy. You should be able to manage all your teams in one tab with a single instance of the app rather than a separate tab with the entire single-page app having to be loaded over and over again.