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

> @oleersoy Speaking of pen vs. pencil, pencil tips introduces fire hazard, see Apollo 1

Wow the joke is actually real.  I though it was just a joke!

> Keeping, the allegory, making small tip set your ship in fire, making lack of is let you loose support for elements with different context, which you cannot rebuild, nor polyfill anyhow, may be pretty expensive.

Maybe but to me it still seems like we are making a 10 billion dollar pen, even though we could just bring our Samsung Note.  Just don't bring the Samsung Note 7.  That one was rushed a little bit [and next month it will officially be useless](http://www.theverge.com/circuitbreaker/2016/12/9/13897794/samsung-galaxy-note-7-update-shut-down-inoperable).

I'm not going to be shocked if the `is` attribute ends up being useful in ways that we have not even thought about yet, but at least get the API design right.  The fact that it's been in play for 2 years and still has not been cleaned up feels like a massive red flag to me.  Doesn't the W3C have a room 30 floors down in the basement where everyone can be locked up and no one comes out until the best solution is drawn up?

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