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

> Any possible improvement for V2 would be welcomed by everyone, but how about we move the Web forward today?

I have to say I love the spirit of this in general.  Some things are stuck in the debate stage forever.  For example the [OAuth2 spec lead resigned](https://hueniverse.com/2012/07/26/oauth-2-0-and-the-road-to-hell/) due to the endless debate over every nuance of the spec.

The next consideration then is how much refactoring needs to be done to the components and apps once they move from V1 to V2?  For example the shadow dom `content` element got switched to a `slot` element.  So now all the components moving to version 1 of the shadow dom that utilize the `content` element have to be refactored and retested.  How much documentation has to be rewritten, etc?

In addition if we had version 2 now, how much efficiency do we gain in the development process for new elements?  

I think if @trusktr suggestions are incorporated into V1 we could end up saving ourselves a lot of time in the long run and possibly gain some goodwill from all browser vendors such that we get this working across the board quickly.  Also if the development picture is prettier, we should be getting a lot more traction with other open source developers.  Right now ReactJS, etc. still seem to be the preferred approach over Polymer, and personally I would love to see Polymer get a boost.


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