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

We can play around with possibly extending a button and inserting custom elements in a table, but these two use cases are a drop in the ocean compared to the millions of applications that will be built in the few coming years without a single custom element that uses the `is` attribute.

As you probably noticed individuals commenting on this thread have already interpreted the `is` attribute as a tool that allows them to create custom styled buttons.

The BIG DEAL is not whether I can show you how to extend a native button.  The BIG DEAL is how do we create a great UX with both native and composite components intertwined that talk to each other and create a great user experience for all users.  This is where the `is` attribute concept falls apart, and is why its value is marginalized to 0.00000000000000000000001%, of use cases if it so happens that it ever gets used.  The only thing that can be accomplished with the `is` attribute is mass confusion.  

Well the entire javascript ecosystem already is already a massive pit of this, we have transpilers, 20 different dialects of javascript, UMD, CommonJS, AMD, Rolling up into FESMS, ES6 Modules or is it ES2015 modules???, or is it a combination of ES5 with ES2015/ES6 modules and why did ES6 need to be renamed to ES2015?

The point is that this stuff is already insanely complicated to deal with and adding yet another concept that adds the same amount of value that a vial of cobra anti snake venom sitting on my shelf here in Chicago adds is crazy.

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