So much more. It’s not even in the same ballpark.

Information for Internet Archive.
MBFC: Left-Center

That’s just embarrassing.

You should probably use a double slash in that non-equality sign as a single slash will be seen as an escape character by some parsers and then not rendered. In my client it just shows two equal signs, i.e. the opposite of what you wanted to convey.

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.

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.

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.

By having the stupid idea of existing next to Russia (or a similar country).

If this was done by multiple people, I’m sure the person that designed this delivery mechanism is really annoyed with the person that made the sloppy payload, since that made it all get detected right away.

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.

TIL there are Linux people that don’t use OpenWRT. I always assumed everyone in the Linux community used it. It’s great.

Works great with mt7621 based routers if anyone ends up looking for something compatible.

I use gnome for the most part. I have been checking out kde recently to see how the newer versions stack up (gave up on it during the 4.0 days). As you mention kde supports dpms changes on wayland because they have their own protocol extension for that.

That’s actually my biggest gripe with wayland - the huge amount of fragmentation it has caused. I’m pretty confident that almost all the missing features I talked about are possible on one or two of the compositors, but not all of them. And definitely not on the one I use. I’m sure once some pragmatism takes hold that all the issues will be ironed out, but my plan for now is to stick to X11 until that happens.

For me it’s a million little details that just don’t work. Stuff like positioning windows, removing decorations from a window, remapping buttons on a trackball, setting a graphics output to tvrgb, disabling a display via ssh and enabling it again, etc.

It’s not just about hardware compatibility. It has to be compatible with existing workflows, and it’s currently very limiting.

set -euo pipefail at the top of every script makes stuff a lot safer. Explanation here.

You tend to lose count after the first few hundred.

I love how the complaint makes even less sense when you look at the KDE mega announcement from yesterday. The third thing listed is a new wallpaper.
Love KDE, but they have some really annoying users.