ensuring fish runs shell scripts properly is pretty trivial - it just runs them in the builtin shell and shows the results

i don’t do anything very special in the shell so fish’s usability features just make life easier

been using it since 3.x and have no complaints

all these experienced lead developers using a new technology to create new software

but you’re the wise one that really knows the truth

oh sorry you’re ml. i hope your delusions are kind to you, heroic commie warrior

yes all of those things are true

you catch on quick. also we extend test suites and our coding style is adopted by C coders because of its god-like superiority

it’s fun watching rust succeed over bad old C everywhere it is used isn’t it?

HIGH FIVE

back in the bad old days yes all the time

not any more

yeah i think this was extremely fair review. if you know what you’re doing windows is not shit. thing is by default for most humans linux will be always better

the monolithic kernel must really mess with your noggin

best of luck with devuan

with a language like rust this actually hardly ever happens

it’s also because they don’t believe the same confused fundamentalist nonsense OP does

haha coming from a nexus user

now do Nix! now do Nix!

jesus that’s a good laptop you could put bazzite on that

Q. You say this is “just attestation, not verification” but we know that infrastructure always gets repurposed later. This is where the legit fear lies. Today it’s birthDate. Tomorrow could it be location, identity, or verification tokens? I understand that you are providing a workaround but where should we draw the line between compliance and resistance?

A. Funny you mention that, location is already a field in userdb. Like birthDate, this field is also trivially nullable, stored locally, and can be set to anything. As long as we are talking about a user self-attesting a date - especially with the ability to enter any value we want - we aren’t in the realm of identity tracking. I draw the line at when a third party internet-connected service is doing validation of ID. Let’s be honest though, I strongly believe such a thing isn’t possible on a FOSS operating system environment unless they could control what was bootable on the device at a firmware level, enforce signatures to ensure that you couldn’t boot something unrestricted, remove the ability to be root, and block LD_PRELOAD so signals couldn’t be faked. There’s probably more ways to circumvent that. What I’m trying to say is real ID verification on Linux would be awfully hard to implement, and I guarantee you, nobody would put up with it. They’d fork to a version that doesn’t have it immediately as a protest. Right now, we’re considering implementing something akin to the date pickers that were ubiquitous when signing up for internet services in the early 2000s where it’s just an honor system. Things like actual ID checks and/or facial scanning + age estimation would be just too incompatible with Linux where we have the freedom to change whatever we want to.

the intellectually diverse lemmings represented in this post and many others cannot understand this

won’t stop them expressing their feelings tho, bless their hearts

don’t tell me you were predicting systemd would destroy linux and you oppose rust being in the kernel got any other takes for us genius?

the lemmy doomers must scratch their suicidal itch

i still have a server running ubuntu

i run snaps on it ewwwww!

it has never fucked me over

good old reddit, must have been a real wrench for you

wait a second what are you doing reading reddit in the first place?

traitor! impure!

i dont believe a single person in this post

why

why

Rust is the future. Notice how the C design committees are scrambling to replicate what rust does while C continues to lay eggs everywhere it goes