Google made Chrome. Chrome had that multi-process architecture at its core which allowed to consume as much memory as needed even on 32-bit OS. Chromium was always inside it and open source. Then they created CEF, which allowed webdevs to build “real” apps, and that opened the floodgates. Electron was first built on it but they wanted to include Node and couldn’t because it required too much experience in actual coding. So they switched to Chromium. It didn’t change much in the structure, just basically invited more webdevs to build more “real” apps (at 1.0 release Electron advertised hundreds of apps built with it on its website). Google could do something about how the web engine works in frameworks (that don’t need that much actual web functionality), but didn’t. They invited webdevs to do anything they want. Webdevs didn’t care about security because mighty Google would just publish new Chromium update eventually. They never realized they don’t need more security in their local “real” apps gui that connect to their websites because there is not much room for security danger in such scenarios. They just always updated the underlying engine because why not. Chromium dll is now at 300 mb or something? All of that code is much needed by everyone, is it not? So, for me the sequence was always seen as this: Google (caring about webdevs, not OS) -> Webdevs (not caring about native code and wanting to sell their startup websites by building apps) -> Reckless web development becoming a norm for desktop apps -> Corporations not seeing problems with the above (e.g. Microsoft embedding more stuff with WebView2 aka Chromium) So yes, Google has everything to do with it because it provided all the bad instruments to all the wrong people. Personally, I don’t care much about hating Microsoft anymore because its products are dead to me and I can only see my future PCs using Linux.