eCos is prior work on OS side that made me always think of designing systems for easy stripping.
why?
would not existing static analysis/dependency pruning take care of it if someone had the time?
I don't see what would be 'novel' here from a theoretical point of view..
still a good project possibly though
Also, I imagine there are many cases where static analysis would not be enough for the JS app.
(not production-ready but it might be soon good enough for really quick GUI prototyping using subset of web technologies - javascript + react + flexbox + styles)
HMR & react-devtools are already supported.
The bridge itself is API stable. evaluateJavaScript:completionHandler: isn't going anywhere.
So the question is whether it's okay to use a native web view while still bundling your own V8 + Node. That seems like an improvement to me!
Historically, this hasn't been the case. Apple loves to deprecate stuff (although, thankfully, they are a bit slower to remove it). Before WKWebView there was a "stable" WebView.
They can't run on native frameworks. If native frameworks are updated old apps would break. If native frameworks aren't updated newer apps would break.
What you're asking was already tried with Adobe AIR and failed. Instead we need lighter alternatives to Node.js and Chromium.