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

@WebReflection 

> we would like to extend native components for graceful enhancement, like it's possible already through the shipped is=""

What is graceful enhancement? Or do you mean progressive web apps? For me, these phrases are just like the famous "Web 2.0": Everyone interprets whatever he wants into these words and wonder why they dont talk about the same thing.

>From my experience, if a client supports CEs (natively or polyfilled), website creators do not want a normal button to be display, that gets transformed to something else _after a while_. they dont want pre-upgrade UX beyond a loading spinner. the problem to solve here is to improve loading time with viable strategies and as far as i understand this is what google calls PWAs (or lets say its one major feature of PWAs).

>From my experience, if a client does not support CEs (unpolyfillable, no JS), website creators do not care about these targets (95%+ of all cases) __or__ do not want to use CEs, if these clients are a target.
Also the primary use cases for CEs are so tightly coupled to being able to execute client side scripts, that trying to make it compatible with NoJS clients feels like non-sense. For NoJS cases stick to server side scripting and "dont try to be cool".
You dont pick a solution and try to fit it with your use case. You pick a solution that fits your use case.

@oleersoy
> Well the entire javascript ecosystem already is already a massive pit of this, we have transpilers, 20 different dialects of javascript, UMD, CommonJS, AMD, Rolling up into FESMS, ES6 Modules or is it ES2015 modules???, or is it a combination of ES5 with ES2015/ES6 modules and why did ES6 need to be renamed to ES2015?
The point is that this stuff is already insanely complicated to deal with and adding yet another concept that adds the same amount of value that a vial of cobra anti snake venom sitting on my shelf here in Chicago adds is crazy.

I cant agree more. And the problem is not understanding a single tool or concept, its about making an informed decision on what to use in your (next) project.

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