chromium.bb

Yes to Chromium, not so much for anything specifically MS-related. Using Chromium as a low-level GDI replacement lets you leverage higher-level constructs and work in web-space to implement rendering, and TS nicely spans between client-side Chromium and server-side V8. Note -- it doesn't need to be specifically Chromium or specifically Node. It just so happens that Node bet on V8 and Chromium is embeddable, so you can get even more leverage out of using the two together. (We actually also use TS with server-side Spidermonkey as well, so TS has definitely proven itself as a better way to interop at the tooling level across these different implementations.) This all comes with a Titantic-iceberg-sized caveat, however. Keeping up with Chromium is difficult. Any embedder is not Google and embedded use cases are not the web. You can leverage a

It depends on what you mean by "rendered". The client side is a highly modified Chromium which runs a GTK like GUI implemented in JavaScript. https://github.com/bloomberg/chromium.bb So it is like Electron in that you are literally interacting with a web-browser, but one made too look like a desktop app.

There are quite a few minimalize Blink efforts. Like this one: https://github.com/bloomberg/chromium.bb https://github.com/weolar/miniblink49 The latter is around 9MB. The author is working on a electron wrapper.