A browser is not a web app, it doesn't have a strict separation of "frontend" and "backend" in the same sense that a web app would have; the lines are drawn qui

A browser is not a web app, it doesn't have a strict separation of "frontend" and "backend" in the same sense that a web app would have; the lines are drawn quite differently. The rendering engine is never "just" the rendering engine; you can't abstract or swap it without tremendous effort. If you'd like to learn more about how a web browser project would organize its internal architecture, but are discouraged by the complexity of Chromium, Firefox, etc. I'd recommend source diving Ladybird (https://github.com/SerenityOS/ladybird https://github.com/SerenityOS/ladybird), NetSurf (https://www.netsurf-browser.org/ https://www.netsurf-browser.org/), or Dillo (https://www.dillo.org/ https://www.dillo.org/).