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.

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.

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)

Of course it is like that. You’re saying that the complaint is wrong because the author doesn’t know the history, and now you accuse me of not understanding you, because I pointed this out.

If you have to accuse everyone of “not understanding”, maybe you’re the one who doesn’t understand.

It’s easy to criticize something when you don’t understand the needs and constraints that led to it.

And that assumption is exactly what led us to the current situation.

It doesn’t matter, why the present is garbage, it’s garbage and we should address that. Statements like this are the engineering equivalent of “it is what it is shrug emoji”.

Take a step back and look at the pile of overengineered yet underthought, inefficient, insecure and complicated crap that we call the modern web. And it’s not only the browser, but also the backend stack.

Think about how many indirections and half-baked abstraction layers are between your code and what actually gets executed.

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.

Stored Procedures have been a thing for literally decades. But they’re an absolute pain.

What would really improve the usefulness of databases are autoindexes and generally more “let me handle that for you”. I’d argue 90% of business apps essentially need a way to store objects and their relationships, but doing that in an efficient manner is really hard (at least if you’ve got a few more rows to handle).

The ranking is perfectly fine, since some of these languages in practice are interchangeable.

You’ll find business software in Java, C#, Python (and VBA, but we’re not talking about that), and you’ll find more system oriented software in C, C++, Rust.

Now, you’re right insofar that it’s misleading to lump all languages together, C and JS rarely compete, but it’s a useful tool to gauge developer/employer pools. If you decide, which language to learn because you want to dip into a new niche, you might not want to learn Steve’s obscure cross-paradigm language (SOCL), but e.g. Rust or whatever is popular.

Same is true for businesses. Yes, your software may be written in really good C, but it’s probably a good idea to go the Java route for the next project, since it’s hard to find 20 new C devs for web apps.

I’m not saying that this specific ranking here is good, its metrics are dubious at best, but the idea isn’t inherently stupid.

My company tried to jump onto the bandwagon in 2018 or so, but it fizzled out very quickly. Fortunately.

It’s the same crap like with blockchain.

People have no idea how sophisticated modern IT systems already are, and if you glue fancy words on solved problems, people will cheer you for being super innovative.