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

> Nobody is forcing us to use is for a customized built-in, but you have the option to do that and leverage PE if you see fit. Seems to me you are not so much rejecting is= but rather PE, even as an optional feature?

If NASA wants to build a 10 billion dollar pen that's their business.  Why should citizens care?  

The spec should be something that moves us forward towards faster, better, and simpler.  We all will be using the API that is driven by the spec.  If that API is simpler we all gain.

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