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

> I disagree, CSS Modules is a generic name that describes the type of module it is

That would be true if there wasn't a _very_ popular project that achieves a similar result with 12,630 stars on GitHub. 

CSS Modules is also built into webpack (via the css-loader) and there's also a plugin for post-css. So there could potentially be confusion for developers in respect to tooling. 

In fact, CSS Modules was also identified by the [State of CSS Survey]() as one of the most popular (and still rising) css-in-js projects: 

<img width="941" alt="Screen Shot 2019-09-28 at 9 09 38 am" src="https://user-images.githubusercontent.com/924/65807002-c7518880-e1cf-11e9-943c-fc31033a6a11.png">

<img width="987" alt="Screen Shot 2019-09-28 at 9 10 39 am" src="https://user-images.githubusercontent.com/924/65807017-dcc6b280-e1cf-11e9-9333-90f7242bfb7d.png">

I think the surface area of "CSS Modules" is a lot more dramatic than first thought. 

> Since the name CSS Modules is never surfaced within the API and is only used in the specification

Given the above, what reasons do you have to keep using the same name? Other than "We've already talked about this before"? It seems to me that there's no upsides to keeping the specification title. 

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