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

> @oleersoy nobody gets hurt ever since the feature has been successfully polyfilled already for the last 4+ years. You are free to not use custom elements builtins, others are free to use those when needed.

When you create something more complex than what is needed that delivers and inferior and buggy ux experience with a paradigm that full of self contradiction there's a lot of pain that goes along with that.  

Most people don't know that though.  Tons of experienced developers used default exports.  I suspect that we will have a 70% education rate about 10 years from now.  Until then we will have produced billions of dollars worth of code and wasted billions of dollars of efforts to maintain and use something that could have been much simpler to start with had we gotten one simple concept right ...




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

Received on Tuesday, 3 July 2018 15:14:50 UTC