News for hackers. Stuff that matters.
Re:Why I Write CSS in JavaScript by itslennysfault on Monday February 18, 2019 @02:29PM (#19193519)
This is the goal of Web Components / Shadow DOM.

Angular implements a polyfill for this. Every angular component has 3 files html, ts, (s)css, and the styles in the components css file are automatically scoped to just the component they apply to. It takes away all the stress of global css selectors, and if you want to share styles you can just have a library of shared styles and import them via scss. It's honestly heavenly and I haven't thought about conflicting selectors in years.

Re:Why I Write CSS in JavaScript by exogen on Monday February 18, 2019 @03:21PM (#19194033)
I'm aware and agree, and it also – even if less so than other solutions like Styled Components – counts as CSS-in-JS. So welcome to enjoying CSS-in-JS :)
Re:Why I Write CSS in JavaScript by deadwisdom on Monday February 18, 2019 @08:25PM (#19195991)
Or use Polymer/LitElement, where it's just all in one file... I swear people are just reinventing react methods to eventually get to where Web Components have been for the past 4 years.
Re:Why I Write CSS in JavaScript by exogen on Monday February 18, 2019 @08:28PM (#19196003)
React is greater than 4 years old, and people mostly use it for the nice authoring experience, not to dick around with CSS isolation problems.
Re:Why I Write CSS in JavaScript by deadwisdom on Tuesday February 19, 2019 @09:07AM (#19198980)
You don't have to "dick around" with CSS isolation problems with web-components, it just works. React is where you are dicking around.