esa

Yeah, none of that with bat:

λ bat $(type -P bat)
───────┬──────────────────────────────────────────────────────────────────────────
       │ File: /usr/bin/bat   <BINARY>
───────┴──────────────────────────────────────────────────────────────────────────
λ bat < $(type -P bat)
───────┬──────────────────────────────────────────────────────────────────────────
       │ STDIN   <BINARY>
───────┴──────────────────────────────────────────────────────────────────────────
λ

Or bat, which will just print <binary> in those cases

Oliven, Norwegian. For some reason it’s an uncountable noun.

Yeah, I think my sway config is around five years old now. The Wayland experience hasn’t been entirely without warts, but as someone who kind of just uses the desktop to drive a browser and a bunch of terminals, there’s not a whole lot of problems to run into either.

Yeah, the left generally considers it a “fighting day” similar to March 8th. The right does gardening (to make it visible that they’re not marching). Others do whatever they feel like; not uncommon to spend the day hung over.

Maybe just the waffle cracker? Because he’s sprø som en kjeks, which works translate as … mad/cracked/crispy as a cracker?

If ssh has a security issue and you permit root logins then hostiles likely have an easier time getting access to root on the machine than if they only get access to your user account—then they need multiple exploits.

Generally you also want to be root as little as possible. Hence sudo, run0, etc.

Kokoro.

Also have vague plans to reread Der Zauberberg

Likely also will reread V. and the Count of Monte Christo at some point.

Nudie is Swedish afaik, yeah.

From Norway we have https://www.lividjeans.com/

I used Ratpoison for well over a decade, and only replaced it with sway once I had a new machine and figured it was time to try Wayland. Apparently that’s some 4-5 years ago already.

You can give her limited sudo rights; even limit her to install and upgrade operations.

Leaking isn’t really the issue, though I suppose Rust helps with that as well. Its memory sales pitch is more about memory safety, which is not reading or writing the wrong parts of memory. Doing that can have all sorts of effects, where the best you can hope for is a crash, but it often results in arbitrary execution vulnerabilities. Memory _un_safety is pretty rare and most prominent in languages like C, C++ and Zig.

Rust also has more information contained in it, which means resulting programs can actually be faster than C, as the optimizer in the compiler is better informed.

Rust is already in the kernel and Torvalds wants more, faster. He’s being obstructed by C purists, who at this point are the people who should fork the kernel if they see anything but C as heresy.

Thing is, there is already Rust in Linux, and Torvalds wants more, faster. He’s being sabotaged by C purists, who at this point should stop acting unprofessionally, or at the very least make their own “only C” fork if they disagree with his leadership so much.

Reads more like if you made a mess as a kid and cleaned up before your parents came home. The state between when they leave and when they arrive is up for experimentation.

How do you know a post was written by a systemd hater? Easy, they’ll spell it with a big D for some reason. It reminds me of how Norwegian rabid anti-cyclists are unable to spell “cyclist” for some reason.

Claiming you don’t want to restart an old debate and then trying to restart it anyway is pretty funny.

You might also want to keep in mind that you can’t really force an init system on Linux distros. Systemd became the norm through being preferred, as in, the people using and maintaining it think it’s good. At this point you might as well be ranting about how “LinuX is evil somehow” and we should all be using GNU HURD or Minix or something.

Also: Haven’t thought about suckless in well over a decade, maybe closer to two? I guess way back in the day I was kinda intrigued by their ideas and used some of their products; these days I’d rather see them as something between an art shop and people who are playing a somewhat unusual game with themselves, but not particularly relevant to mainstream software engineering.

It’s ultimately up to oneself to decide these things for oneself, but there is literature on the topic. Part of it you can just frame like the stories themselves: Is it worthwhile to read or watch a story unfold, rather than just read a summary? Is there any point to anything that ends? You know a good meal with your loved ones is going to end before you sit down—but you still choose the meal over going hungry and alone. Because the experience has value even if it ends. Some experiences are even valuable because they only existed a brief moment in time.

There are, ultimately, some stories that are so mired in despair and suffering that anyone would close the book early, but most of the stories are kind of trudging along, with their own motivations, hopes, fears and joys.

To quote another work on the topic: One must imagine Sisyphus happy.

Yeah, while -e has a lot of limitations, it shouldn’t be thrown out with the bathwater. The unofficial strict mode can still de-weird bash to an extent, and I’d rather drop bash altogether when they’re insufficient, rather than try increasingly hard to work around bash’s weirdness. (I.e. I’d throw out the bathwater, baby and the family that spawned it at that point.)

Yeah, there’s also a subtle difference between ${1:-} and ${1-}: The first substitutes if 1 is unset or ""; the second only if 1 is unset. So possibly ${foo-} is actually the better to use for a lot of stuff, if the empty string is a valid value. There’s a lot to bash parameter expansion, and it’s all punctuation, which ups the line noise-iness of your scripts.

I don’t find it particularly legible or memorable; plus I’m generally not a fan of the variable amount of numbered arguments rather than being able to specify argument numbers and names like we are in practically every other programming language still in common use.

Yeah, another way to do it is

#!/bin/bash
set -euo pipefail

if [[ $# -lt 1 ]]
then
  echo "Usage: $0 argument1" >&2
  exit 1
fi

i.e. just count arguments. Related, fish has kind of the orthogonal situation here, where you can name arguments in a better way, but there’s no set -u

function foo --argument-names bar
  ...
end

in the end my conclusion is that argument handling in shells is generally bad. Add in historic workarounds like if [ "x" = "x$1" ] and it’s clear shells have always been Shortcut City

Side note: One point I have to award to Perl for using eq/lt/gt/etc for string comparisons and ==/</> for numeric comparisons. In shells it’s reversed for some reason? The absolute state of things when I can point to Perl as an example of something that did it better