Reply To: DOM vs Virtual DOM

[__]

Just reading + watching at this point. I don’t know how soon I’ll be trying to actually build something.

It’s got this abstraction layer built in that takes away all the BS you have to deal with … Great. But… aren’t we back to having markup, style and logic mixed?

Well, what about hyperlinks? form elements? video? They all have styling and behaviors that are pretty much “baked in.” I don’t think the idea is to push all style and logic into the markup, but the “standard” stuff — yes, why not?

Concerns are still separated (perhaps more so, in fact): you have an HTML template, a scoped stylesheet, and then your scripting. The difference is that these things are no longer in the main document. They’ve been modularized.

It encourages you to think about what you’re doing, as well. I’m sure there will be some people who build a polymer-menu element with fixed pixel dimensions and hard-coded menu items, but …really, there is something of a “natural pressure” to put the standard, “always-desirable” features into the element itself, and leave the more specific details to css/js in the main document. Custom elements, yes, but they’re meant to be dynamic and reusable, not one-offs.

edit

Speaking of the google-maps element, wouldn’t you like a mapbox element??