leisesprecher @ leisesprecher @feddit.org

Posts

2

Comments

643

Joined

1 yr. ago

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.

Train nerds are a weird bunch.

Please never change.

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.

That's not what I mean.

This company is a scheme to finance Trump's campaign from foreign sources. The foreign investors are "suckers", in the sense that they lost money on their investment, but they still achieved their goal: funneling money to Trump.

All the retail investors and MAGA heads are just collateral damage.

Not "unfortunately", but rather "exactly as intended".

This entire business is essentially a money laundering scheme.

What frightens me about all of that is how many people don't see through that bullshit. It's so extremely obvious how full of shit these demagogues are, but millions of people applaud for that.

Here in Germany we had state elections. On the "anniversary" of the invasion of Poland ⅓ voted for an openly right-wing extremist party, and 10-15% for a party that basically claims to combine the national with the social, both parties are supported by Russia. It's insane.

That's the funny (or sad) thing with almost all of those free speech enthusiasts. They don't want free speech, but exclusively freedom for their speech.

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 DBAs. I'm currently working on a project where I said from the very start, I can set up this DB in k8s and I can get it to work decently, but I have neither the knowledge nor the time to get it right. Please give me someone who knows how this works.

No, don't worry, it'll be fine, we don't need that, this kuverneles thing I keep hearing about handles that!!!

Six months of hard contact with the enemy on production later:

Well, we're currently looking for someone who actually knows how DBs work, because we have one of those issues that would cost a proper DBA 5min and me 5 months.

To be fair, a lot of roles simply disappeared over the years.

Developers today are much more productive than 30 years ago, mostly because someone automated the boring parts away.

A modern developer can spin up a simple crud app including infrastructure in a day or so. That's much much more productive than 1995. We just cram a lot more of the world into software, so we need 20x the amount of developers we needed back then.

It's really weird, though, that nobody really created a language/tool to bridge these two world. It's always just generating one representation from the other, mostly in a bad way.

I'd argue, that for many problems, a graphical view of the system can help reasoning. But there simply is nothing in that regard.

It's all just pointers with semantics attached.

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)

Vaporware.