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

@oleersoy : Who is NASA in your allegory?  

If I could sum up, I believe you are saying **you support customised built-in elements,** but you also say they should **not be allowed** to have built-in syntax (which enables an important aspect of PE), because it costs somebody something, who's purse you're looking out for.  

But beyond the cost of implementing customised built-in elements of the hyphenated variety (which may be significant I grant you, but which **you** are arguing for i.e. the 9.9 billion dollar pencil), what could be the cost of the non-hyphenated variety of customised built-in element?   And not implementing that feature has a cost to others who **want** to enable that PE; they'll be more likely to build native apps for example.  Not to mention the cost to the evolutionary aspects of the Web that I already mentioned.

Thank you


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