Very interesting read! One question I have is, since the architecture involves quite a thick client on top of base Chromium, and the client seems to be platform-specific (Swift/OSX in this case), how is the team thinking about the overhead of building all this for each platform -- Windows and Android specifically, but also perhaps iOS?
Mobile is a different story for sure and for many reasons. We will be bringing this same architecture to Windows. It will fit it well there, and in many ways Windows is already well suited for multi-process configurations. It always has been.
Glad to finally be able to share Atlas with the world last week! There's a lot of novelty under the hood. While Atlas is using Chromium, it's not built on top of Chromium in the usual way.
As one of the engineers who designed and built Chromium's multi-process architecture back in the day, it is really cool to take it to the next level.
Very interesting read! One question I have is, since the architecture involves quite a thick client on top of base Chromium, and the client seems to be platform-specific (Swift/OSX in this case), how is the team thinking about the overhead of building all this for each platform -- Windows and Android specifically, but also perhaps iOS?
Mobile is a different story for sure and for many reasons. We will be bringing this same architecture to Windows. It will fit it well there, and in many ways Windows is already well suited for multi-process configurations. It always has been.
Glad to finally be able to share Atlas with the world last week! There's a lot of novelty under the hood. While Atlas is using Chromium, it's not built on top of Chromium in the usual way.
As one of the engineers who designed and built Chromium's multi-process architecture back in the day, it is really cool to take it to the next level.
[dead]
They recreated Electron.
Electron works differently. It runs in process, similar to how a normal Chromium embedding works (like Chrome itself).
[dead]