{"id":29120,"date":"2020-06-02T15:44:02","date_gmt":"2020-06-02T19:44:02","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=29120"},"modified":"2021-05-28T20:54:56","modified_gmt":"2021-05-29T00:54:56","slug":"rebuilding-slack-on-the-desktop","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/06\/02\/rebuilding-slack-on-the-desktop\/","title":{"rendered":"Rebuilding Slack on the Desktop"},"content":{"rendered":"

Mark Christian and Johnny Rodgers<\/a>, writing last year (also: Hacker News<\/a>):<\/p>\n

Today, after more than half a decade of hyper-growth, Slack is used by millions of people with larger companies working with more data than we ever could have imagined when we first started. Somewhat predictably, a few internal cracks were starting to show in the desktop client’s foundation. Additionally, the technology landscape had shifted away from the tools we chose in late 2012 (jQuery, Signals, and direct DOM manipulation) and toward a paradigm of composable interfaces and clean application abstractions. Despite our best efforts to keep things snappy<\/a>, it became clear that some fundamental changes would be required to evolve the desktop app and prepare it for the next wave of product development.<\/p>

[…]<\/p>

However, moving to a multi-workspace architecture was quite the undertaking. We couldn’t expect every function call to pass along a workspace ID, and we couldn’t just set a global variable saying which workspace was currently visible since plenty of things continue to happen behind the scenes regardless of which workspace the user is currently looking at.<\/p>

The key to our approach ended up being Redux<\/a>, which we were already using to manage our data model. With a bit of consideration and the help of the redux-thunk<\/a> library, we were able to model virtually everything as actions or queries on a Redux store, allowing Redux to provide a convenient abstraction layer around the concept of individual workspaces. Each workspace would get its own Redux store with everything living within it — the workspace’s data, information about the client’s connectivity status, the WebSocket we use for real-time updates — you name it. This abstraction created a conceptual container around each workspace without having to house that container in its own Electron process, which was what the legacy client did.<\/p><\/blockquote>\n\n

Ben Sandofsky<\/a>:<\/p>\n

\n

Rather than write two separate native apps, Slack has now written a cross-platform app four different times.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n