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

From a veteran frontend developer: Honestly I don't care how popular any library is, or how it has been sitting on a name. All the alternatives suggested - and how much they suck - clearly show that the library **must** step back here and rename their project. Standards - and consistent naming in standards - **is way more important than any third party stuff**, no matter how popular it is.

Anything other than **CSS Modules** as a name for the W3C Standard seems unacceptable to me.

Remember we're not talking "break the web" like was the case in the `Array.prototype.flatten` story. We're just asking for a popular library to rename their project. Honestly, I don't even find their name very fitting for what it does (which to my understanding is rather "Scoped CSS" - another very generic name that I wouldn't advise either).

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

Received on Monday, 8 June 2020 16:38:59 UTC