Re: [w3c/webcomponents] Change 'CSS Modules' name to avoid webdev confusion (#843)

There are two separate issues I'm seeing, if it's useful to have this reflected by an observer:

1. Is the naming confusing?

I believe the answer to this question lies in deciding whether the two approaches are aimed at the same use cases. If so, great! The platform is evolving in the direction people want. This work should probably deprecate this other CSS Modules project, eventually. If these are wildly different, wholly incompatible, then it may make sense to imagine another name as it would be surprising if the same description applied to two very different things.

2. Are the authors of the existing project aware of and included in this conversation?

If this is superseding the existing project, that should be only a positive thing for the authors and maintainers of the CSS Modules project who are now not only responsible for inspiration and prior art, but also on a path towards being able to target a platform that provides out-of-the-box support for some of what they're doing. This can only be a problem if they feel the work here falls short of what they want and that they had no input.

Can anyone speak to these things specifically? Is there (at least a sub-set of) the CSS Modules project that is directly, deliberately, and similarly covered here, such that it really does refer to more or less the same thing? Are the authors and maintainers of the CSS Modules project aware of this work, this thread, our hand-wringing and do they feel invited, or what can we do to make them feel so?



-- 
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/843#issuecomment-536779384