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.

They were also wise to not have revealed the Switch 2 any earlier, because it would have jeopardized sales of the Switch 1. Enough companies have made this mistake in the past.

Ah, the Osborne effect…

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.

I wish people would remember that after 8 years of explaining.

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.

Some editors can embed neovim, for example: vscode-neovim. Not sure how well that works though as I never tried it.

Well personally if a package is not on aur I first check if there’s an appimage available, or if there’s a flatpak. If neither exist, I generally make a package for myself.

It sounds intimidating, but for most software the package description is just gonna be a single file of maybe 10-15 lines. It’s a useful skill to learn and there’s lots of tutorials explaining how to get into it, as well as the arch wiki serving as documentation. Not to mention, every aur or arch package can be looked at as an example, just click the “view PKGBUILD” link on the side on the package view. You can even simply download an existing package with git clone and just change some bits.

Alternatively you can just make it locally and use it like that, i.e. just run make without install.

Aur and pacman are 90% of why I use arch.

Also fyi to OP: never install software system-wide without your package manager. No sudo make install, no curl .. | sudo bash or whatever the readme calls for. Not because it’s unsafe, but because eventually you’re likely to end up with a broken system, and then you’ll blame your distro for it, or just Linux in general.

My desktop install is about a decade old now, and never broke because I only ever use the package manager.

Of course in your home folder anything goes.

I think they meant you don’t know what the binary is called because it doesn’t match the package name. I usually list the package files to see what it put in /use/bin in such cases.

What’s up with the abuse of the word open lately. I had a look at that project to see how they were doing the conversion, but I couldn’t find it. But I found this:

Short answer, yes! OpenScanCloud (OSC) is and will stay closed source…

Your data will be transferred through Dropbox and stored/processed on my local servers. I will use those image sets and resulting 3d models for further research, but none of your data will be published without your explicit consent!

I feel like I’d rather use Autodesk at that point. At least I know what I’m dealing with right out of the gate.

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

I mean I learned it in a few days and found it very intuitive as well. Far more intuitive than I found fusion when I tried that years later. Inventor and onshape also feel more pleasant to use.

The issue seems to be that the fusion interface is very non-standard when compared to other cad suites, so people that get used to it first find everything else unintuitive.

I live in a qwertz ISO layout country, but I use qwerty ANSI layout keyboards because I find that text editing is better with them. Makes finding a laptop pretty hard though.

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.

It’s not over… It’s joever!

Someone found a way to weaponise bikeshedding.

Everyone just confirming aliteral’s point.

I never said I don’t enjoy spicy food. But it’s so obviously a dick measuring contest for most people. No one talks about how much salt they can “handle”, no one makes fun of people for not being able to stomach a really sweet energy drink. But with capsaicin it’s so prevalent, it’s a whole subculture dedicated to pissing in a line. I mean this whole thread is only popular because the initial proposed underlying thought is “haha, Denmark can’t handle spice”. It’s all very juvenile.

Yeah, I get it. You’re cordless, right?