gentoobro on Nostr: Part of the problem is that browser projects tend to be so monolithic. You can't ...
Part of the problem is that browser projects tend to be so monolithic. You can't readily extract individual components of a browser and mix and match them, replacing or improving some of them.
The best approach to the general problem of browsers is for people to start making small, lean, self-contained, minimal-dependency projects that handle individual parts of a browser, like parsing CSS files, parsing HTML files, calculating HTML layout and CSS layout rules (but not actually rendering) and of course a lightweight JS compiler. All in C of course; anyone wanting to integrate with another language can use the FFI or write a native wrapper around the lib.
The best approach to the general problem of browsers is for people to start making small, lean, self-contained, minimal-dependency projects that handle individual parts of a browser, like parsing CSS files, parsing HTML files, calculating HTML layout and CSS layout rules (but not actually rendering) and of course a lightweight JS compiler. All in C of course; anyone wanting to integrate with another language can use the FFI or write a native wrapper around the lib.