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.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.