That's very nontrivial task, if feasible at all, considering current overcomplicated state of affairs in CSS, HTML, JS, graphical, font-rendering and networking fields of browser's interest.
> Guys, there is a _reason_ why microkernels suck. This is an example of how things are _not_ "independent". The filesystems depend on the VM, and the VM depends on the filesystem. You can't just split them up as if they were two separate things (or rather: you _can_ split them up, but they still very much need to know about each other in very intimate ways).
Re:Firefox is on a slippery slope
by thomastjeffery on Monday December 18, 2017 @03:10PM
(#15954999)
> That's very nontrivial task
I imagine so.
And?
we are slowly working towards this goal[0], we try to team up with other projects and develop this stuff cooperatively. our focus is on the user and developer experience side of things. creating good comfy tools for developers and fighting for very high quality UX on the user side.
[0]: https://heropunch.io
Yes, that is a lofty goal. That does not make it unreasonable.
> Is the solution to break that into its component parts, so that each part can be maintained by a smaller group, and composed together to produce the browser as a whole?
Possibly, but currently, a "web" browser depends on its monolithic qualities. A web page is a DOM, defined by HTML, styled by CSS, and manipulated by JavaScript.
I think it may be time to start designing something less inherently monolithic.
One advantage to modularity is that we don't need to finish before we can use it.