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

> I name template and you ignore it.

Every time you show me something that is an example of how to go about using `is`, it's something that does not need to use is.  Your `x-map` example does not need `is`.  You decided to ignore that.  So go ahead pimp out `template` for me.  SHOW ME me the demo??

> I name tr and you ignore it.

Demo??  You can name things all day that does not make a case.

> html is a unique tag and for a singel page app it makes perfect sense to use it as cusom element and enrich capabilities asynchronously as soon as the JS is downloaded in a non blocking way ... but you ignore it

Not at all.  You can do that perfectly well without `is`.

> So I think it's clear there's nothing you are looking for, you just want to keep stating your point of view. 

No - I want the web platform to be as simple as possible to work with and I want rapid progress, and things like this are delaying the party.

> Yeah, we got it, you don't have the need for is while the 80% of developers in here do.

No they don't and that's why you can't produce a single case where they actually do. 

> and I'm done here.

Yes you are because you have nothing of value to add.






  

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