问HN：为什么我们没有像glibc或DirectX那样共享的“libchrome”？
过去几年，跨平台桌面应用程序的现状主要依赖于 Electron，但这也意味着每个应用几乎都要捆绑一个 Chromium，这并不是理想的解决方案。那么，为什么我们不开发一个类似于 Linux 中的 glibc 或 Windows 中的 DirectX 的 libchrome 呢？想象一下，如果每个游戏都要捆绑自己的 DirectX 版本，那将会是什么样子。我想，主要的障碍在于稳定性，glibc 的变化不大，但 Chrome 却在不断变化。不过，我觉得通过维护一个长期支持（LTS）版本的库，这个问题是可以轻松解决的。之前有人提出过这个想法吗？Chromium 作为一个引擎，是否与 Chrome 作为桌面应用的逻辑耦合过于紧密，以至于无法将其作为库进行发布？
查看原文
The status quo of shipping a cross platform desktop app easily for the past years have been electron, but this comes at the cost of pretty much shipping a chromium with each app which is not ideal. So why don't we have a libchrome like we have glibc in Linux or DirectX in windows. Imagine every game would bundle their own DirectX version with them. The big blocker I imagineis stability glibc doesn't change much but chrome is constantly changing, but I feel this is easily fixable by maintaining a LTS version of the library and calling it a day. Has anyone pitched this idea before. Is chromium as an engine too coupled in logic with chrome as a desktop app making it impossible to ship it as a library?