I think the problem lies with the definition of consent more than with the definition of suffering. If the alternative is something worse, then that’s not consent. That’s coercion.

Now, whether it’s still appropriate to still call it suffering when applied to someone enthusiastically consenting, I’m not sure.

See also: the Linux Kernel

Fair enough. I just thought it had become pretty ubiquitous in the desktop ecosystem, just because HDMI licencing fees are egregious

Every single monitor I’ve seen that’s built in the last 8ish years has at least one. All modern graphics cards do too. Are you sure you’ve not seen them?

RISC-V :'>

Were you?

Not sure why they show it like that, it might be a design choice. Where I live, it’s often put as decimals, with the last digit smaller than the others:

9/10 of a cent

It’s about the certainty to have what you want, where you want it, reliably. I run NixOS with Impermanence, which means I reset my root partion on every boot, and have what state I need specifically opt-in. And I run a shared config over multiple devices (home PC and Laptop), so installing something on one also installs it on the other, next time I rebuild. It certainly takes time getting used to, but I’ve been really enjoying it so far

Look at the perspective near his hands, either it’s the most crooked console ever or it’s AI

pointless summation, that just simplifies to n(n+1)/2 :P

I want my terminal to just work, so all this kitty stuff is overboard for me, but good for them!

Helix!

Oh I agree, I am happy with Helix and use it as my main editor already. I like that they’d rather take their time to figure out how to make plugins work well.

Uhhg, I’ve been waiting for module support for helix for forever, now. It’s a planned feature, but it’s been that way for ages now

:3

It’s less so the wider tech-industry, as in corporate big tech. But the general open-source community and hacker spaces in particular have a lot of trans and other queer people in it

Factorio puts game saves in ~/.factorio for some reason…

It’s fair to want to learn (and it’s certainly a good skill to have), but the question is what you’d rather see in a large, production environment. Guard rails are usually there for a reason. As for the control: you actually can program memory-unsafe (and in kernel development you often have to!) in Rust. The difference is that in Rust it’s explicitly marked by an unsafe block:

unsafe {
  ...
}

That way you get the same, fine-grained control over low-level processes, but someone else reading your code can at a glace spot where potential memory bugs may be.

In the end, languages are a tool. Especially for personal projects, everyone should just go with what’s fun to them. I personally think it makes sense, logistically, to slowly transition legacy C-based projects to Rust, because it makes onboarding new developers easier, while keeping the same memory safety that requires years of experience otherwise, basically for free. But there’s really no rush to rewrite anything that’s working well in Rust

it’s pretty bad. steam for example has both
~/.steam and
~/.local/share/Steam
for some reason. I’m just happy I moved to an impermanent setup for my PC, so I don’t need to worry something I temporarily install is going to clutter my home directory with garbage