Comments on: “If” CSS Gets Inline Conditionals

By: Mirko

Mirko — Fri, 12 Jul 2024 10:37:47 +0000

Some other comments cover almost everything I hate about working in this field. They are shortsighted, opinionated, solely based upon one’s very own needs and some are even hostile against others.

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?

By: Kev Bonett

Kev Bonett — Thu, 11 Jul 2024 07:29:54 +0000

My brain hurts!

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.

By: Bitten

Bitten — Thu, 11 Jul 2024 02:57:04 +0000

In reply to Solomon.

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.

By: Novembrine

Novembrine — Wed, 10 Jul 2024 16:22:59 +0000

In reply to Dallas Ransom.

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

By: Solomon

Solomon — Wed, 10 Jul 2024 07:23:32 +0000

I hand never needed to use if conditions in css. I think this goes against what css is meant for, which is a cascading stylesheet… cascading being the key weird here. This is further complicating a simple and beauty language into something it’s not meant to be. KISS

By: Dallas Ransom

Dallas Ransom — Wed, 10 Jul 2024 00:41:28 +0000

Apart from not needing anything like this, this will be a terrible day for CSS if it gets implemented. The good thing about CSS is that it’s still relatively unscathed by idiot programmer influences – but adding this will open the floodgates to all sorts of dumb stuff.

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.