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

> I’m not sure that it’s the naming that is really going to confuse people

What do you base this on? Have you had experience with people saying "oh this thing is named the same thing as this other, different thing - no problem!" or similar?

> The APIs being 95% the same

Am I reading this right that you are arguing that the similarity of the APIs is a problem? If so, that's not really the point in this issue here...

> when someone learns ES/JS Modules and then JSON Modules and some HTML Modules, then they’ll really be confused when it’s not also CSS module they learn next
> are we sure this larger conversation is actually serving the purpose intended in these cases as well?

Does this seem like a common learning path to you? It seems a bit contrived... I would expect most module systems to be covered together in one block in most learning materials (if they do get standardized).

---

For the record, I actually agree about consistency being generally a good principle in systems design.

However, my main point is that the drawbacks of confusion outweigh the benefits of consistency.

---

I think that if you would like to continue this discussion, we should continue this on Twitter - we are not adding much more than noise to the other participants here at this point.

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