DSS, a deterministic way to manage CSS
What problem is this trying to solve? I don&#x27;t see what benefit there is to generating a unique CSS class for each individual style; it just seems like a reimplementation of inline styles.<p><i>In addition to that with atomic CSS your application bundle size grows, i.e., at some point, you can keep adding CSS, but the file size of your CSS bundle won&#x27;t change (increase).</i><p>It should be noted that this is absolutely not true if your application uses static rendering. Sure, you might be able to avoid multiple references to the same CSS rule in your stylesheet but now your compiled HTML is even more bloated. A button from any given CSS framework takes 5-12 CSS rules to look decent. Now imagine creating a unique class name for each rule and applying that to every button on the page.<p>There&#x27;s also the issue of swapping styles in the browser to get a sense of how things look. I maintain an internal admin UI where the navbar is styled differently depending on the environment to avoid a developer accidentally affecting production data. It&#x27;s a lot easier to swap `.dev` with `.prod` on an element than it is to swap out all of these class names or restart my web server, overriding the environment. DSS also means that your developers will have to sift through a lot of useless noise when inspecting the DOM; pull up <a href="https:&#x2F;&#x2F;dss-lang.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;dss-lang.com&#x2F;</a> in your browser&#x27;s DOM inspector and tell me if that&#x27;s something you&#x27;d enjoy working with.