Curious about your roadmap with dosyago and BrowserBox, where our goals converge and diverge and how we can help each other. Feel free to reach out via email, it's in my bio.
Here's some other projects you might have inspo or crossover with and some discussions you might find possible collaborators in:
Bonsai https://news.ycombinator.com/item?id=28446147
Mullvad Browser (security oriented FireFox-based) https://mullvad.net/en/browser
Browsh (purely text-based browser) https://news.ycombinator.com/item?id=17487552
Ladybird (browser from scratch for SerenityOS)
Kosmonaut (browser from scratch in Rust) https://news.ycombinator.com/item?id=24170201
Refresh (concepts for a new kind of web browser) https://news.ycombinator.com/item?id=17638477
Really though? Why
While it may not be as technically elegant as using lisp, it greatly increases the count of folks who can contribute and simplifies the code with a single language for both front and back.
Secondly, while, in general terms, JavaScript is not as performant as Java or C++, for asynchronous real time operations, such as mostly used by this application, the event loop in node, a layer over io_uring, is a highly highly efficient method to perform these.
In other words, we get to trade simplicity for raw performance to ease maintainability, and less complex code means less security risk and bugs. In fact, the bottleneck in this application for performance is not JavaScript but network link latency, and the browser and the hardware that runs on.