8 ms·

Don't understand why so many of these ideas keep popping up. What is so wrong about CSS that devs need to find alternatives to work around having to declare sty

Don't understand why so many of these ideas keep popping up. What is so wrong about CSS that devs need to find alternatives to work around having to declare styles using the CSS language?

tenken 5y ago
The most general complaint I've seen in the past is that legacy css was not able to be DRY without a preprocessor. Current css versions support some variables I believe ...
- nawgz 5y ago
  I still don't think you can make a block or an assignment using CSS vars, i.e. the left hand side of a `property: value;` statement. Maybe I'm wrong, that would be interesting
  - royal_ts 5y ago
    yes you can, it's known as css custom properties
    - easrng 5y ago
      I think they're trying to say that you can't :root { --prop: color; --value: red; var(--prop): var(--value) }
- cxr 5y ago
  > css was not able to be DRY without a preprocessor This is really nutty, though, considering that so many of the projects where these sorts of things find adoption are exactly the ones that are wont to inject bloated frameworks and brittle tooling into the publishing pipeline, anyway. Stop removing semantics from markup; keep attaching real class names to things. The class attribute is about more than providing a handle for style sheets to bind to with CSS selectors.