re: The journey of Web Components: wrong ways, lacking parts and promising paths VIEW POST

TOP OF THREAD FULL DISCUSSION
re: The problem as I see it lies in choosing improper abstraction. There is no need for such components to be in the DOM, and to query from the DOM j...
 

Thanks for the explanation. Do you think that having that model code in the DOM was error prone or insecure, or is it strictly a matter of separation of concerns?

I think both statements are valid to some extent.

Storing data (especially, when it comes to application state) in DOM is one problem, attempting to use DOM for meta programming is a different one.

Interestingly, trying to solve the first problem could sometimes result in leaning towards the second one, as we can see it when looking at github.com/google/uniflow-polymer

In my opinion, all these problems have been implied by the two way data binding system and how it affected the way of thinking of Polymer users.

code of conduct - report abuse