Hacker News Reader

In the SASS days I rarely found myself using the more advanced features and native CSS variables/nesting kind of killed the appeal for me altogether. But libraries and approaches like that really pushed the standards a bunch and it seems like a strong pattern going forward versus just waiting around for RFCs.

There are some quirks and syntax to these CSS functions I don't love, but I won't complain when we're using basic web standards stuff across the board.

I’m in this boat. CSS variables are nice for removing hacks and frameworks from my code. Both are things I welcome.

I still use SCSS just for the comment syntax. It cost me nothing to use in Svelte.

Being able to easily do multi-line and nested comments when working on a design saves a non-zero amount of time and brain cycles.

HTML and CSS comments are the absolute worst.

> ... [CSS functions] will simplify hack-ish CSS and open a lot of new possibilities.

If this is the goal, I'd rather see the spec updated to address the "hack-ish CSS" directly rather than introducing functions to the mix. This seems to be making CSS more complicated rather than simpler.

It's making CSS more complicated and CSS codebases more manageable.

This is really cool, but, who's asking for this? UI framework developers? The CSS spec is getting wild.

Functions in CSS?