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 when people started writing books instead of memorizing epic poems.

It’s usually not a question of legality, but efficiency.

It’s easy and efficient to bust someone for seeding, but busting hundreds for the odd file you can prove they downloaded is expensive and takes forever.

And let’s be real here, it’s not too rare, the current victims simply don’t count as much.

All those “tropical” diseases seem to be completely irrelevant as long as only poor people in a developing country get it. But as soon as a good white person dies, it’s defcon 11 and suddenly it’s really important to develop something expensive to help the rich countries.

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.

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.

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.

Vaporware.

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.