I luckily don’t have to modify scripts these days so I’ll just use bash to run them if there’s no better alternative around. And usually it is, few things are only available as bespoke shell script

1. Types.

   You explode lists manually into items when calling commands on a variable list of arguments instead of “quoting variables” to prevent them from exploding.

   Who came up with the bullshit idea that exploding strings into words is such a common use case that this footgun is preferable to have an “explode lists” syntax?

2. Errors. No more set -euo pipefail; shopt -s lastpipe to beat some semblance of sanity into bash

That’s a paradox. POSIX shells are all bad because POSIX demands bad syntax.

You can have pain word strings without also having weird “variables auto-explode into words” bullshit.

That’s why I use nushell. It has lists. You do cmd ...$some_list to call a command on arguments from a list.

By now there’s an always-enabled service running that updates the keys from time to time. So this won’t happen anymore on servers.

Always have been 🔫

The kind of bullshit I’ve seen here on Lemmy alone.

I think “i have this hardware and want to utilize it optimally” is peak Linux.

That’s the thing: you shouldn’t need to get identical monitors for technical reasons. And Wayland is much closer to that goal.

On average, yeah, but when it’s worse, it’s the most bafflingly bad.

Like why is the only way to be able to open files in a hidden folder to remember a keyboard shortcut? There’s no icon, and you can’t type a subfolder name.

Windows’ weird UX of having that temporary view setting in the context menu makes no sense, but at least I don’t have to Google how to do it every time.

It’s crazy that you still get replies after you constantly make shit up and tell others what they believe.

No, more like as if this is the straw that broke the camel’s back

The comment does contain tips on how to set it up though

I’m an Arch user. I check the diffs when I update a package. I won’t do anything as I’m obviously not compromised.

Hahaha I’m old enough to get that one, but I’m sure there are zoomers going “tf they’re talking about dogs now”

Welp, you wouldn’t be the first who actually believes what you wrote!

So far I’ve just checked the diff of every package update. But with that many, I think we should maybe start using using the script provided in the article that you evidently didn’t read.

That’s not how that works.

• when you use distribution-provided packages, you trust the distribution maintainers
• when you use the AUR you trust the upstream project and check the PKGBUILD because the maintainer can change

In some cases, upstream also maintains the AUR package, in which case you can probably trust that it’ll not be abandoned

Arch usually doesn’t re-package Python packages that aren’t needed for something else, meaning they end up in the AUR. I maintain several there, and when I stop using them I abandon them. I wouldn’t be surprised if some of the ones I used to maintain are on the list

Arch actually has a large amount of official packages. Maybe some of the packages you’re referring to are just slightly renamed or alternate versions?

It’s possible that in some areas it has fewer packages of course (e.g. Debian might repackage a larger subset of PyPI as Python packages), but I need the AUR for very few things.

Paywall.

And then your auto-formatter removes them in a blink.