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

> Repeat again, default export is simply a "syntax sugar", so I don't think it will need "ton of education" in this simple case.

Not true.  It allows us to redefine randomly what a module exports when we import it.  That then can lead to multiple collisions when attempting to refactor in order to adopt a new naming convention.  

1) Something as simple a going from camel case to underscores becomes impossible.
2) The risk of refactoring naming collisions goes up drastically because we now have random names all over the place.
3) Tree shaking a massive object that a junior developer created requires either new tooling (Which takes a while to fix - Check rollup or parcel issue log) or we just don't do it.

We could easily avoid all these and the repercussions by using named exports.

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