And who does that?

I think you don’t really get my point. I’m not arguing that there are no ways to archive data. I’m arguing that there are no technologies available for average Joe.

It is hardly a good strategy to basically set up half a datacenter at home.

Thin concrete slabs are extremely brittle.

Is it? It’s rather expensive and would you really know, if the data is gone or corrupted?

You’d have to download every single file in certain intervals and check it. That’s not really low complexity.

But what actually is “archival”?

Like, what technology normal person has access to counts at least as enthusiast level archival?

Magnetic tape, optical media, flash, HDD all rot away, potentially within frighteningly short timeframes and often with subtle bitrot.

The long-term goal is for Rust to overtake C in the kernel (from what I understand

Your understanding wrong. Rust is limited to some very specific niches within the kernel and will likely not spread out anytime soon.

critical code gets left untouched (a lot of the time) because no one wants to be the one that breaks shit

The entire kernel is “critical”. The entire kernel runs - kind of by definition - in kernel space. Every bug there has the potential for privilege escalation or faults - theoretically even hardware damage. So following your advice, nobody should every touch the kernel at all.

Germany has a Sovereign Tech Fund for exactly this, and while it’s not perfect, it’s one of the better uses of my tax euros.

Replacing C with Rust in the upstream kernel is akin to replacing the engine in a car while it’s running or being used every day.

That’s in no way what’s been proposed. Rust is used in a very well defined niche, nobody wants to get rid of C.

But it’s just that sentiment that got us here, you’re arguing against a non-existent threat, and thus reject the whole proposal.

And it’s a bad argument anyway. You’re only good at memory management until the first bug takes down production.

Rust isn’t a panacea and certainly has problems, but eliminating an entire class of potentially very dangerous bugs is a very good argument.

and I could make a death ray out of my home wifi box and a wok.

I mean, you could. Do you happen to have a small nuclear reactor and about 400l of liquid helium?

It’s absolutely not inherently wrong or implausible to assume that the constant and rather direct exposure over decades causes cancer.

Old timey radio operators definitely died earlier. They had much higher cancer rates. Granted, completely different levels of radiation, but radiation damage is stochastic. If there is an effect at all, it will cause thousands of new cases even low doses simply because we have like 7 billion phone users.

Doing proper studies on that is hard, but absolutely necessary.

Well, obviously, you just have to put a sticker with a geometric pattern on it to turn the bad radiation into good radiation!

(I wish that was a joke, but you can actually buy those)

No, I’d argue you simply didn’t want to invest in the other tools.

Think about it, you probably spent hours on customizing and automating vim, and then say you’re faster in that. Well, that’s called a habit.

IDE are objectively more powerful and since you can actually see options and navigate quickly, you don’t need to memorize every obscure feature.

All the terminal editor enthusiasts are actively holding us back, because they insist everything outside vim is garbage for enterprise and kiddies.

If your tool of choice is actively hostile to new users for no reason other than “that’s how it’s always been, and thus it’s better”, well then you’re digging a moat to automate your gatekeeping.

I understand it very well. And that’s exactly why I’m writing this.

Ok, I can see you have no idea what you’re talking about.

Then say, grandmaster delusion, what purpose does vim serve, where it is actually the best tool? Writing code? Hardly, it’s way too limited and requires a ton of upfront investment and headspace. Writing config files? Hardly, because if you write these by hand, you’re living in the 90s, that’s what Ansible, Terraform etc are for.

You just don’t want to admit, that vim is nothing more than a habit. Muscle memory.

You’re using the terminal, because you’re used to it. It is not the better tool, it’s simply what you happen to know already.

People who argue with productivity because of some key bindings live in the world of the 80s. You don’t just sit there and type code 12h a day, that’s not how modern software development works.

And all those blockheads down voting me are caught up in their weird superiority complex. They are the powerful superhackers, and don’t understand that we are just highly qualified plumbers.

…so your infrastructure is outdated.

And how often does that happen in the real world?

VIM may have been a very useful tool 20 or 30 years ago, but today it’s nothing else but a tool for one’s sense of superiority. It’s the vinyl of editors.

If you have to type that much code in a terminal, your infrastructure is outdated. Simple as that.

And that’s especially true for Linux and other big projects.

I’m not a kernel or C developer by any stretch, but a few years ago fixed a small bug that caused my knockoff PS2 controllers to act super weird. Nothing serious, something like one constant and maybe 5 lines of code. Would have gladly pushed that upstream, but fuck me sideways is that a complicated process. Patches via email??? And the argument is always “but it works for us”, yeah burning witches and slavery also work for some people, doesn’t mean it’s something to continue doing.

If there isn’t a serious revamp, Linux will die a slow death or become just a corporate graveyard product like Cobol.

He’s still on YouTube, in case you didn’t know.

What really bothers me is that rpi seems to have “lost its way”.

I’d argue, there are essentially two camps here. The close-to-x86 camp, who want powerful, but efficient small machines, and the tinker-board camp, who want cheap machines with barely any power needs, basically a microcontroller on steroids, that you can buy an entire school class worth of for a few bucks.

Rpis started in the latter camp. 35€ for reasonable performance, great software for kids to tinker with, hardly any requirements, everyone has a usb mouse/keyboard.

But nowadays pis are in the no man’s land between. They’re priced above cheap N100 PCs, but are not as powerful, and simultaneously way too expensive and involved for throwing them at children - like it was initially intended.

I’m not sure, how that’s supposed to be sustainable.

Actually, the Pico is also an arm device, just the M0 variant which admittedly barely counts as a computer.