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

> It's about whether it's confusing for the average developer

it's apparently not, read his comment which was:

> even I understand the is concept

Keeping talking FUD about how difficult is for everyone to understand `is=""` which has been used and understood for the last 2 years is not moving anything forward.

Talking about alternatives that do not cover what `is=""` covers already is also not moving anything forward.

Web developers are tired of these new but never trust-able APIs and every dev that believed and used what Web Standards proposed got it, swallowed the "_not perfect_" solution, and move forward **adopting it**.

People against `is` attribute in this thread are only those that never used it and never investigated why it's needed, I've honestly no idea why we're still talking about it because there's nobody to convince about its usefulness, just propaganda about not having it, without valid alternatives for today needs.

I start believing myself this thread should be closed. It's bringing literally nothing to the discussion, including my over-stated comments.

Best Regards



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