As they point out at the end, this wasn’t about the old control panel, but the new settings panel. It’s all brand new code.

It’s worth noting that this is a new line of ThinkPad, there’s a bunch of existing lines that will all keep the classic look. Though I feel like the name X9 isn’t great, but whatever.

The issue isn’t just a simple oversight. Git includes the file name as part of the tree and commit hash. The hash has security implications. There’s really no way to make the hash support case insensitivity without opening up a multitude of holes there. So there will always be a mismatch, and you can’t just fix it without changing how git works from the ground up.

Podman not because of security but because of quadlets (systemd integration). Makes setting up and managing container services a breeze.

But check that it has all the features you need because it lags behind gitea in some aspects (like ci).

Podman quadlets have been a blessing. They basically let you manage containers as if they were simple services. You just plop a container unit file in /etc/containers/systemd/, daemon-reload and presto, you’ve got a service that other containers or services can depend on.

I’ve been in love with the concept of ansible since I discovered it almost a decade ago, but I still hate how verbose it is, and how cumbersome the yaml based DSL is. You can have a role that basically does the job of 3 lines of bash and it’ll need 3 yaml files in 4 directories.

About 3 years ago I wrote a big ansible playbook that would fully configure my home server, desktop and laptop from a minimal arch install. Then I used said playbook for my laptop and server.

I just got a new laptop and went to look at the playbook but realised it probably needs to be updated in a few places. I got feelings of dread thinking about reading all that yaml and updating it.

So instead I’m just gonna rewrite everything in simple python with a few helper functions. The few roles I rewrote are already so much cleaner and shorter. Should be way faster and more user friendly and maintainable.

I’ll keep ansible for actual deployments.

Not sure what you’re on about, most package managers have a literal database of most package manager installed files. Debian and derivatives have dpkg --verify or debsums to verify the files, arch has paccheck, I’m sure other distros have something similar. And fixing them is just a matter of reinstalling the package, which you can do from a chroot if the system won’t boot.

Or you can just run your system on a checksumming FS like btrfs which will instantly tell you when a file goes bad.

Someone found a way to weaponise bikeshedding.

All public companies are, it’s just what Boeing makes things that fall out of the sky if they mess up, so it’s more obvious.

Just have NAS A send a rocket with the data to NAS B.

Seems to me that a lot of the world’s problems start with “well, the managers think…” They all seem extremely bad at the whole managing thing, good thing we don’t overpay them or anything like that.

Or libcinder. Or even simply Arduino.

That’s a very arbitrary delineation that just seems to be something you worked out backwards to support your claim. I’m an EE and software developer and I sometimes do projects involving both fields (which would be computer engineering, I guess), and there’s really not that much difference. I certainly don’t see why I would label half of it engineering and the other half not.

Yeah OpenCASCADE is amazing because it’s the only real geometry kernel that’s open source. There’s a few smaller ones like solvespace, but they’re really more like toys. It’s like the Linux of the CAD world.

Writing a geometry kernel is a monumental task, not unlike writing a real os kernel or a modern web engine. I’ve seen people just lay the basic foundations of a kernel as their PhD thesis. Most of the commercial ones were written decades ago and are still being worked on - the big ones are Parasolid ACIS, ShapeManager, CGM. The last one would maybe be considered a newcomer cause it’s only 15-20 years old.