he/him 
YouTube's UI is still built with Polymer 1. They did test with Polymer 2 but they're kinda... stuck at v1 to this day
Show this thread
-
This is a bit unfair. We had the specs change underneath us right after 1.0, and we spent considerable effort making incremental migration possible.
What specs were changed? Haven’t Google been championing all the Web Component specs?
-
-
Custom Elements and Shadow DOM both changed from what we now call v0 to v1. This is when Apple, Mozilla, add Microsoft agreed to implement.
-
That just seems like a risk for implementing a spec that doesn’t have consensus and approval. I don’t think it’s the vendors fault at all and it feels like deferring blame.
- 6 more replies
New conversation -
-
-
Lifecycle, element definition, class versus prototype, etc http://polymer-library.polymer-project.org/2.0/docs/about_20#custom-elements-v1 …pic.twitter.com/bkNxgkfJm0
-
It feels like “nobody implemented our spec verbatim so it’s their fault we had to change and break compatibility”.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.