It was an embedded system. The user wouldn’t be able to download and install stuff, they just turn the thing on.
As someone who likes to actually own and customise all my devices, devs like you are the bane of my existence. Read up on software licensing, and pay special attention to the history of its enforcement and what it enabled us. Then please reconsider your user hostile stance.
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.
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.
Just have NAS A send a rocket with the data to NAS B.
I really like gnome the software, but I’ve started considering moving away from it after a decade simply because of how toxic and difficult gnome the project can be.
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.
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.
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.
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.
I remember seeing a thread about redis on r/linux where lots and lots of people were basically defending Amazon as if from an anarcho-capitalist position. This confused me as I always saw foss (and foss users) as leaning socialist and anti-corporate.
I spoke to someone about that and they linked me this article (and the article linked in the first sentence) which really opened my eyes.
The TL;Dr is basically: