Re:CSS sucks because we don't bother learning it (2022)
by the_other on Monday January 05, 2026 @04:51PM
(#46505509)
> constants
Constants which you can redefine/shadow in scopes, and change the values of at runtime via JS.
They seem like variables to me.
Re:CSS sucks because we don't bother learning it (2022)
by marcosdumay on Monday January 05, 2026 @10:53PM
(#46508546)
> and change the values of at runtime via JS
No, you can't. You can set a new value and reevaluate everything.
Re:CSS sucks because we don't bother learning it (2022)
by the_other on Tuesday January 06, 2026 @01:23PM
(#46516324)
I’m dumb and don’t understand the distinction you’re making.
elem.style.setProperty(‘—var-name’, newValue);
… will set a new value for the “constant”. The element will rerender with the new value. You can animate/automate these changes and the element will continue to rerebder with the updated value.To me, that justifies the name “variable” from the perspective of the CSS.
It's just not one based on states, mutability, and variables. Even the things that use the `var` keyword are constants, not variables.
(But then, don't read that as being against scoped rules. The fact that all rules are global to the document is bad. We can emulate scopes with specific selectors, but that's the kind of thing a language is supposed to help with.)