We can have nice things, just not forever.

Shopify's CEO is also part of this whole Omarchy funding shit too. So, now tailwind, the CSS library I have used for years... is loosely in that orbit.

I'm pretty sure I should just go back to rolling my own flexbox library per project at this point.

On top of that, Shopify is a company that had numerous anti-consumer practices, seems to be gobbling up things left and right, and proudly advertises their AI bullshit left and right. They are not a trustworthy party.

I’ll give my reasoning. Or at least one story from a compendium of many.

There is an OSS library called ktlint for Kotlin. It is a “no bikeshedding linter” that was supposed to be based on the default rules from JetBrains. That is, if a rule existed already from JB then ktlint would enforce it and if the rule wasn’t specified it would make and enforce a new one that the community agreed on.

That was all fine and dandy until I and some others pointed out that one of the rules was the exact opposite of what JB had specified. When called out the owner of the repository didn’t care, until too many people were against his choices that he couldn’t ignore it anymore. He made it configurable.

So the rule was fixed. Until he sold the repository to Pinterest. Pinterest just wanted to own ktlint so they could control the rules. They immediately changed it back and made it non-configurable. When pressed on it, they just refused saying it wasn’t going to be that way anymore. They didn’t care what the community wanted they just wanted to control the rules for themselves.

The repository is open source, but they took the most widely used Kotlin linter and essentially stole it from the community. Getting enough people to switch because of one rule will never happen.

Why is this a bad thing? Sounds like they are leaving it open source with the existing MIT license. The potential for a rug pull exists of course, but that potential exists whether or not they got bought.

We just can’t have nice things

Based on my tests, it works with Safari though not in Firefox.

No.

and CSSWG recommends using OKLCH for gamut mapping.

I followed the link to section 14.2, but don't see any such recommendation. (Excluding subsections, which seem more specific; unrelated to a recommendation.)

All three CSS gamut mapping algorithms aim at constant-lightness, constant-hue chroma reduction in the OkLCh color space.

Maybe we should be using RGß instead.

"Wow, it's super cool and superior and better"

Not one comparison side by side. Had to check one of the links - https://evilmartians.com/chronicles/oklch-in-css-why-quit-rgb-hsl#comparing-oklch-with-other-css-color-formats

Compared to normal RGB hex, it's just "more readily readable", which is ok, I guess? For CSS, which users rarely have a chance of changing, this isn't a big deal.

No sign of even an eta for support in Firefox, sadly. It's pretty new, so hopefully other engines add it soon.

AI;DR

you have to earn dark mode by reading the blog enough to write a nice dark mode userstyle

Oh come on. It is 2026. Add a dark mode to your blog. You literally write about CSS.

Identify all your .scss files. This can be with AI or a simple Find operation. You just need a list to work through.

Why oh why would you even suggest AI for this when the simpler solution is right there that you know for sure will work?

You can use the value system-ui in your font-family in CSS, you get a font that represents the default user interface font. Meaning you get something kinda Windowsy on Windows, Linuxy on Linux, and Macsy on macOS, etc. It’s well supported across browsers and platforms. I think it’s a good choice for many situations.

Firefox does not support scroll-driven animations

Into the trash bin it goes.

Nice, I see it works well. Personally I don't get the reading indicators and predicted read time info. It gives me the impression the writer thinks i'm either stressed / short of time or that I entered a reading competition. I read because I want/need the info or because I like the book. If not, I quit reading it. So, even though it's not for me, it's still nice and I hope it served it's purpose end keeps you from burning out.

Goldilocks looks very close to gridlock which looks very close to another word at a glance:3

Good ol' CSS-Tricks. Thanks for this one.

There was (and still is) definitely a push when sass came out to make everything “easier” by making it more complex.

Yeah, it’s sad. People forgot how to use CSS properly.

$colors: (
  primary: blue,
  danger: red
);

@each $name, $color in $colors {
  .text-#{$name} {
    color: $color;
  }
}

Although, rarely used in such a simple example.

Good to see this kind of articles. Nowadays there are no real reasons anymore for CSS preprocessors.