Frameworks (as the most popular currently exist) have always felt like the wrong conceptual approach for building complex webapps. That is, if you're going to

Frameworks (as the most popular currently exist) have always felt like the wrong conceptual approach for building complex webapps. That is, if you're going to go through the trouble of shadowing the DOM, creating "components", etc., then why expose the DOM at all and why make those components HTML-bound? Why surface CSS by default? A framework could completely abstract away the messy Web semantics that make webdev so painful. Use a GUI for laying out the UI and let it generate the HTML. Use an event-driven component model for "true components" that don't carry the weighty mishmash of CSS, templates, and code. Rather than go back to vanilla, it'd be interesting to explore going forward beyond Web semantics and protocols. That feels more like evolution.