https://en.m.wikipedia.org/wiki/List_of_countries_by_life_expectancy

Nope, 65th place, slightly behind the US and the country of old men: Albania.

And a whole lot of content that I frankly would have preferred not to have seen.

When you’re 12 and your parents have no idea what you’re doing, you’ll end up in very dark corners.

It’s the same in China.

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.

And when people started writing books instead of memorizing epic poems.

And just about 5 of them have the same capacity as an iPhone battery. Absolutely insane.

Had to work with a fixed string format years ago. Absolute hell.

Something like 200 variables, all encoded in fixed length strings concatenated together. The output was the same.

…and some genius before me used + instead of stringbuilders or anything dignified, so it ran about as good as lt. Dan.

And there are some truly magic tools.

XSDs are far from perfect, but waaay more powerful than json schema.

XSLT has its problems, but completely transforming a document to a completely different structure with just a bit of text is awesome. I had to rewrite a relatively simple XSLT in Java and it was something like 10 times more lines.

Python caches bytecode, so the translation happens only once.

Java loads everything immediately and keeps it in memory. All beans, all connections, etc. That takes up a ton of memory.

Of course, but I’m not productive in it.

If I have to do everything myself, it will take more time to get it done. The trade-off is of course always control/speed vs convenience, but C is definitely too inconvenient for me.

Not that limited. Limited means an old thin client, not a microcontroller. I already set up a small web server on a pi pico with mpy, so it’s quite impressive. But from what I understand, the interop with “MacroPython” is not that great.

Did you use mpy for x86 devices? Are the limitations worth it?

But that would mean either using Graal/native image or going full Scala, right?

I only used Scala for Gatling, where it’s obviously very java-y.

There’s nothing to really grow. It’s mostly just small helpers. Aggregate sensor data, pull data from A and push it to B every hour, a small dashboard, etc.

C is too involved for my case , I want to be productive after all.

Rust is already rather low level, though there are some cool looking frameworks.

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.