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

Man I was meditating all peacefully --- Wooooza.  OK - @hax suppose that the default export in `./exports.js` which we currently refer to as `doSomething` in one import and `doSmth` in another as shown below..

```
// in file import1.js
import doSomething from "./exports.js"
// in file import2.js
import doSmth from "./exports.js"
```

Now the author of the export file decides to change the semantic meaning to something more specific like `DoTheDew`.  How do the files importing the default export  from `./exports.js` get refactored with the new semantic meaning (`DoTheDew`.)?

I'm repeating myself here (Sorry @csuwildcat - I tried), the parallel for that with the `is` attribute is that the `is` attribute implies two states for the client delivering whatever contains the `is` attribute.  One where the `is` attribute falls back and another where the full capability is delivered.  And the original assertion in the Google document I came across was that this was THE way to deliver progressive web apps, which is NUTS.  Show me one app that can do this well (Stackblitz, Google Keep, ...) and is popular and I'll never comment again, and I know that just by me saying that there's 20 devs right now pulling 3 all nighters on this.    



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