I've been saying the same for years. As long as we are working directly with HTML, we will have these impedance problems. The component/event model a la Swing

I've been saying the same for years. As long as we are working directly with HTML, we will have these impedance problems. The component/event model a la Swing et. al. is a far more elegant match for modern Web development, which is now essentially the same as building window-based native applications. OTOH, HTML was designed for static content delivery. Even if a framework must generate some HTML to remain compatible with browsers, there's no reason we have to work or think in HTML as our central interface model. Give me a canvas, let me lay out (and style) components, then let me respond to events.