> to phase out the current browser technology while building something that applies the lessons learned from the current web and build something that is simple and powerful.
Yeah, I do remember couple of HTML/CSS rendering implementations in Java applets so we've been there, seen that.
As of React …
React is a Scottish dance for just being able to get didMount/didUnmount calls on custom elements, that can be accomplished way easier. Yet use of diff algorithms (polynomial complexity, sic!) for just populating DOM is kind of too much …
It’s a pretty awesome app.
https://www.figma.com/blog/building-a-professional-design-to...
Most technical issues can realistically be tackled. I doubt you could win against Google et al. on the tracking/code execution stuff.
I'm pretty ignorant of how desktop apps work; how simple is it? Are we talking a straight up pub/sub system?
The whole browser facing side of the web is a mess. I think it's quite similar to C++'s situation. Because we require backwards compatibility, the standard is becoming an unmaintainable mess and the best plan would be to phase out the current browser technology while building something that applies the lessons learned from the current web and build something that is simple and powerful. I think WebGL and WASM would be a good way to start. That way we could build a new browser inside the old browser and once the new browser is stable, we can build the old browser inside the new browser and let it have it well deserved EOL. I'm usually in favour of fixing existing solutions than to start from scratch, but the current web is such a badly engineered mess that it warrants a rebuild.