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

The thing that I think is really strange about this still is that we now have to explain the progressive enhancement concept to new developers who may have just learned html and have put in charge of assembling both custom elements and current html spec elements into a page.

The first thing that struck me is that it sounds like we are now OK with FOUC.  Before it was something that we would hide until all resources are loaded and everything works and now it almost seems like FOUC is fine.  The second thing is that we now have to explain that if you have `<my-foo>` and `<your-foo>` and they are supposed to work together then just forget the whole thing.  So now the explanation is already starting to sound like a [**CrazyHack**](https://www.html5rocks.com/en/tutorials/webcomponents/imports/)

CSS and html can both be pretty daunting when first starting out.  And now we are adding a fairly massive switch to that, and it can lead to a lot of confusion.  

If you have a penny and flip it you have 2 different results.  Pretty easy to understand.  If you have two you can have 4.  If we have 3 then we can have 8, and so on.  For each penny we add there's lot more combinations grapple with.  

We could say that we are only going to use `is` in 1 penny type situations, but if that's the case can't we come up with simple?  What about just having `<my-foo`> and it works because we have precached the resources that make it work.  End of story.  We took one penny out of the learning curve for all future developers.   

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