Have you even tried to look at it from other viewpoints? Have you tried to find practical use-cases for it outside your current bubble? One of the benefits could well be to finally not be dependent on certain types of CSS/JS frameworks anymore. It could be the next step towards a vanilla web development. Towards easier to implement styled web components. Towards easy to set up, fully customizable theming. Towards even more DRY, compact CSS.

Honestly, I see a lot more pros than cons. My cons being more on the side of performance and syntax. But those are exactly the things the working group is for, to either sort those out or say “nah, not worth the effort”.

Those comments look like hasty calls for stagnation; change isn’t welcome. Would this mindset be prevalent, we would still be sitting in front of CRTs, use the bgcolor attribute and do table layouts like in the late 1990s, early 2000s. Ah, strike that! We would probably still paint cave walls with ochre paints.

Also, in regard to the hostile comment mentioned above: Calling others idiots, arseholes or dumb. Really? Someone’s in need for self validation here?

However, I’ve used conditionals in my Sass code for years. For example, passing args into mixins, and testing for their values.

Hopefully this native behaviour will become a reality one day… but without creating some sort of “Frankenstein” syntax to achieve it.

Agree with all comments, utterly strange hype for a completely pointless abstraction.

What pray tell will set the success variable value true or false?

Yeah the same code that worked to toggle a classname or conditionally alter the styles currently.

All this does is confuse devs on where to look if bugs occur since functionality could be in css or code now.

It also will make testing functionality just a tad more difficult.

It has been done https://dev.to/thormeier/dont-try-this-at-home-css-as-the-backend-what-3oih

The next thing you know some arsehole will code a web server out of CSS and this will usher in a new era of super abstracted, inscrutable UI frameworks that will require a some kind of node extension to run and will require a web server restart everytime you make a change, further preventing devs from actually learning CSS.

If there’s a developer out there that actually thinks this is a win for CSS then they probably shouldn’t be writing CSS. Stick to Java or C because you wouldn’t know how to code layout if your life depended on it.