Did you consider building this on top of Chromium? It has to be so much more work to recreate a browser, securely. I mean, certainly, it is more than one dozen people can handle in a lifetime. Was there something about Chromium that doesn't work on a basic level?
> Did you consider building this on top of Chromium?
Currently, the Browser UI is actually just a PWA pointing to the nodejs instance and is reusing whatever rendering engine is available. I want to have a clean codebase, so everything is babelfree es2018 and will only run in edgium and safari 12+ (and chrome 70 or webkitgtk or webkitqt or firefox etc).
For mobile my plan is to bundle nodejs-mobile and just use a webview there, which is based on chakra (so it is JIT free and is technically allowed on iOS). For desktop I will probably unclutter servo modules and try to have a minimal fork that doesn’t have all the web apis I don’t want or need...but I’m not sure, as I’m not yet familiar enough with the servo codebase.
One thing is sure: I can’t create a competing rendering and layouting engine, so I gotta reuse an existing one.
