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

Yeah, the CSS Modules library squatted not only on a name, but also on syntax. There's a reason why `import` is a reserved word and any project squatting on that syntax implicitly accepts that their syntax might interfere with the platform moving forward.

Is it unfortunate? Yes, but then again, I shouldn't create a feature that uses the `implements` keyword despite the fact that it isn't currently used in JS and expect that the implementation details (no pun intended) won't change in the future. The CSS modules library kind of broke the contract. I don't mean that to be vitriolic or disrespectful, I really enjoy using that library, it was just a bad choice of a name.

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