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

I've never found `is` confusing. Not elegant, hacky, everything but confusing, really.

Other buzz words are just developers choice, as you can see they love confusion so they create thousands slightly different bundlers while HTTP2 idea is to not need them at all.

However, this stat about 0.00...1% is confusing, and I've no idea where does it come from.

Custom Elements have been one of the most problematic standard to deal with, and without my polyfill (or the polymer on) nobody would've used them: constant changing, specs with parts ignored by few, implemented by others, limited usage, etc.

I've written [examples](https://github.com/WebReflection/ce-examples) and [fixed transpilers](https://github.com/WebReflection/fix-babel-class), promoted and advocated Custom Elements with or without the rest of the Web Components family for years, and I keep feeling their limited application.

You can invent new things but never improve what's there.

To do that you need to ignore vendors and specifications and target directly nodes or their prototype.

Like I've said already, I'm OK with that, I just wish we could've found a better agreement here.


-- 
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-302916516