esa

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.

One rather obvious reason is that society has a lot of greybeards in general. The baby boomer generation was named that for a reason, and people have been living longer on average. Lots of countries are struggling with the demographic effects. There’s no reason to expect that tech or something even more specific like FOSS would be exempt.

Another aspect here is that FOSS is still kind of new in society. There’s just more people who have had the chance to age into FOSS greybeards than when those greybeards were young. (And they were thus likely to a lesser degree blocked by entrenched greybeards when they were getting started.)

This needs some work to reconcile with how Trump appears to act towards the pretty poor Russia vs the wealthy EU, though.

Likely he’s just personally uncomfortable with powerful allies, and would rather have weak & subservient underlings. That this would leave the US worse off seems to be a sacrifice he’s willing to have the Americans make.

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.

Yeah, it’s essentially a weathervane or thermometer. You can indicate the state of a country by it.

At this point the US has joined the ranks of, well, grim theocracies. Not that the people at the top in the US worship anything but Mammon.

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.

When the leader of the world’s largest superpower dreams of Anschluss of their otherwise allied neighbour, that’s not clickbait, it’s the state of international policy and diplomacy with the leader the US elected.

not the “I have no mouth and I must scream” future, just the “I have a mouth and I must groan” present

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.

I had to figure out how to do the factory reset at the gym after I got the blue triangle of death when leaving work. Oddly enough it synced the gym plan I wanted and leaving it connected to the phone didn’t seem to produce any other ill effects, but I stayed away from anything using GPS.

But yeah, the general advice for Garmins just now seems to be “just don’t” and hope it doesn’t triangle itself until the fix is out

They’re stuck in a reboot loop, but not bricked. A factory reset works (but the problem may reappear on update).

Better jobs. I would never have had the kind of career growth I had staying where I used to live.

Side note here: Better access to work-related events. It is possible to WFH for some jobs that were previously city-only, but you’ll be missing out on not only the casual socialization of stuff like grabbing a pint after work, but also various technical meetups. I’ve gone to meetups for fields of work not related to me just because I find the topic interesting and it’s easy to swing by.

Central Oslo resident:

• Gym is about 8 minutes by bike away. I’ve gone to gyms further away to train with my PL club but ultimately the gym between here and work wins out (work is about 10 minutes by bike away).
• Groceries are usually five minutes by foot away. Within ten minutes on bike I have access to bigger and more specialized shops.
• There are plenty of bars within walking distance, with various concepts, so we can visit one we’re in the mood for.
• Quiz nights in bars are generally packed. They also frequently have board games available, but I tend to ignore them.
• It’s actually pretty quiet here. There are some noisy party streets, but you more or less just need to live a block or two away to not hear any of it.
• We also have plenty of parks and easy access to the waterfront for Sunday Spaziergang and swimming.
• IMO Oslo could learn a bit from German cafe/Konditorei-culture. We have good coffee pretty much anywhere, and some good pastries here and there, but not their cake selection. There’s also plenty of restaurants around, again within walking distance. Depending on our mood we can just get a döner and watch Star Trek at home, or we could go out to eat at something mentioned in the Michelin guide, or something in between, or even get Foodora. (The Frau was severely pleased when one of her favourite places got a Bib Gourmand.)

A significant difference for the household economy is if you can own your home in the city and not have to own a car. The home will appreciate, while a car depreciates. Generally energy costs will also be lower if you share walls with your neighbours. And, of course, being two helps. Living with a friend or two in a collective is pretty common.

But also going to work and getting groceries is something almost all of us have to deal with. We have to wipe our asses in the city, just like everywhere else.

The bathrooms in the building need to be refurbished and I’m actually thinking of getting a Japanese style toilet with a built-in bidet.

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

#!/bin/bash
set -euo pipefail

if [[ -z "${1:-}" ]]
then
  echo "we need an argument!" >&2
  exit 1
fi

I’d interpret vertical content growth as content per area, deep story lines, stuff like that. It’s a common enough comment, see e.g. MMO players complaining about “content drought”.

The logs are handled, but I mostly use it for command separation and control, including killing unruly child processes.