3 ms·

First Debian is a distro composed of several third party software. The closest equivalent to browsers in scope in Xorg and that has gone in maintaince for being

First Debian is a distro composed of several third party software. The closest equivalent to browsers in scope in Xorg and that has gone in maintaince for being unmaintainable. Web browsers could be simplified if designed differently(internal architecture). We browser are monolithic programs but with stuff like nodejs, gjs, web view, pwa, etc. , Parts of browser must really become system library (that has some stability) and daemon that run on login. Aka the solution to the bloated web is modularisation of certain components.

ktpsns 5y ago
Interesting idea, but what would be the advantage of having, for instance, the javascript engine running as a system daemon? This reminds me of Windows Script Host, which was some similar idea but didn't make it. What we see instead are JITs or VMs such as the JVM, node or any other language (such as raku or julia) which just work standalone, in the same way as a browser does.
- marcthe12 5y ago
  Is engine prob is better of a s a system lib. The Daemon are for stuff like service workers from pwa, they are already boardline apps(notifications for example). The biggest advantage of the system lib style is you can effectively share with native program. It also standard cross platform. A not so bloated nodejs and electron setup.
  - ktpsns 5y ago
    I agree with the system library, and this should be standard. A system library and a system daemon are two different concepts, thought. HTML engines as shared libraries were common in the past (thinking of KHTML or mshtml.dll) and still are (thinking of Qt WebEngine or WebKitGtk). They are not that popular any more because devs want to have 100% control about the concrete engine version and quirks, so they prefer shipping their own engine, as with Electron. I feel that there is a strong rejection against Electron-like application development/shipping.

ktpsns 5y ago

Interesting idea, but what would be the advantage of having, for instance, the javascript engine running as a system daemon? This reminds me of Windows Script Host, which was some similar idea but didn't make it. What we see instead are JITs or VMs such as the JVM, node or any other language (such as raku or julia) which just work standalone, in the same way as a browser does.

marcthe12 5y ago
Is engine prob is better of a s a system lib. The Daemon are for stuff like service workers from pwa, they are already boardline apps(notifications for example). The biggest advantage of the system lib style is you can effectively share with native program. It also standard cross platform. A not so bloated nodejs and electron setup.
- ktpsns 5y ago
  I agree with the system library, and this should be standard. A system library and a system daemon are two different concepts, thought. HTML engines as shared libraries were common in the past (thinking of KHTML or mshtml.dll) and still are (thinking of Qt WebEngine or WebKitGtk). They are not that popular any more because devs want to have 100% control about the concrete engine version and quirks, so they prefer shipping their own engine, as with Electron. I feel that there is a strong rejection against Electron-like application development/shipping.