Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

posting my (now removed) edit because you answered to fast:

beyond that fitting target requirement, the only things that prevent me from hopping onboard the webcomponents train right now are an underdeveloped ecosystem compared to vDOM frameworks. With the ecosystem problem hopefully getting solved in the next 6-12 month, we then have a vDOM-comparable platform feature that is (or should be) more performant, than vDOM.
A bonus would be to being able to reuse or target client native behavior (like the <select> mobile presentation), but i dont think we should sacrifice a streamlined DX for that (a sacrifice which is="" is for many)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/509#issuecomment-303044325