tldr;

ms cleartype isn’t always compatible with oled.

This article is about a machine running macOS. Nothing to do with Cleartype in here at all.

Didn't MacOS remove any form of subpixel hinting like 6 OS versions ago?

The OP seems to have a problem not only with fonts but also with straight lines in CAD.

OP is me, and yeah, AFAIK they did.

It's a problem with how this subpixel problem aligns with my use (mostly static content with high contrast edges) at the display scaling I'm using.

It just doesn't work for me, so until I can get a more traditional pixel pattern OLED at a price I'm willing to pay I'll just go back to LCD.

On the contrary, more and more repos are using RST recently.

For me this is the superior format, but alas, almost no one uses it. Even Python projects usually go with.md docs. What new projects have you seen using.rst docs?

Well, now they can only ship half baked stuff twice a year.

They should at least be shipping monthly updates with the months security updates. Well some months have not had any since Google is now trying to batch them to be quarterly because OEMs couldn't keep up with monthly security fixes.

The problem with automatically applying whatever crap that is stored in git, means that you cannot reverse anything without a long heavyweight process, clone code, make a branch, create a pr, approve a pr, merge to master/main.

That can take hours, and that’s not acceptable when PROD is burning.

That’s why most places don’t dare syncing to prod automatically.

> The problem with automatically applying whatever crap that is stored in git, means that you cannot reverse anything without a long heavyweight process, clone code, make a branch, create a pr, approve a pr, merge to master/main.

Nonsense. Your process is only as complex as you want it to be. Virtually all git providers allow you to revert commits from their GUI, and you can configure pipelines to allow specific operations to not require PRs.

As a reference, in push-based GitOps it's pretty mundane to configure your pipelines to automatically commit to other git repos without requiring PRs. This is the most basic aspect of this whole approach. I mean, think about it: if your goal is to automate a process then why would you go through great lengths to prevent yourself from automating it?

What’s the (practical) difference between section 3 and 4? Please explain.

The system should undo state drift even if a run hasn't been prompted by changes to the upstream definitions in the repository