If you live in the USA you don't suffer from the problem it solves because you have ~5 IP v4 addresses per capita (totaling to 41% of all the IP v4 addresses), and likewise many european countries have ~2 per capita (although there are expeptions like Italy and Spain which are a bit under 1 per capita). However many other countries don't have such luxury, for example in india there's one for every 36 people, which is obviously not enough and thus they have to either use NAT everywhere or switch to IPv6.

Insanity is when you lose or can't access your 2FA device and you're locked out of your account.

Where's the punch?

In the face of everyone expecting an upgrade

More like Windows showing ads even when you boot Linux

Because Rust is not the only language that made this faulty assumption. It is an issue that affects Rust's stdlib, just like it is an issue that affects Python's stdlib and other libraries. In fact this was first reported as a vulnerability to yt-dlp (where it was actually exploitable) and then discovered it applied to many other libraries (where the exploitability is highly dependent on how the feature is used).

Rust here is only used as clickbait because of its aim to be "safe", but its position is no different from other languages.

If you read the article from the researcher that discovered the vulnerability you'll see they never call out Rust in particular, only as part of a list of languages that are affected. https://flatt.tech/research/posts/batbadbut-you-cant-securely-execute-commands-on-windows/

Even after reading the key points it wasn't clear "how" they manage to do that. The article is not much more detailed, but at least mentions them exploiting android's accessibility services.

To be fair trees still use energy for doing this, but that energy is conveniently provided by the sun.

Even in english this isn't true, for example dots can appear inside a sentence for multiple reasons (a decimal number, an abbreviation, a quotation, three dots, etc, etc), which would make you split it into more than one piece.

But the one time I looked at a rust git repo I couldn't even find where the code to do a thing was.

IMO that tells more about how the project was organized and names things than the language used.

So I think probably, the best way IS to go the way linus did. Just go ahead and write a very basic working kernel in rust. If the project is popular it will gain momentum.

As the other commenter pointed out, there's Redox. The issue is that this completly disregards an incremental approach: you have to rewrite everything before it comes usable, you can't do it piece by piece. Currently the approach of Rust for Linux is not even to rewrite things, but to allow writing new drivers in Rust.

Trying to slowly adapt parts of the kernel to rust and then complain when long term C developers don't want to learn a new language in order to help isn't going to make many friends on that team.

Have you seen the conference video? That's not just refusal to learn a new language, it's open hostility. And it's not the only instance, for example Asahi Lina also reported unreasonable behaviour by some maintainers just because she wrote Rust code, even when Rust was not involved.

To run something on multiple cores you need to detect a bunch of different tasks it is doing that don't depend on one another. Then you can execute each task in its own thread. The problem is that most often these different task don't exist, or, if they do, figuring them out automatically by the code is likely equivalent to solving the halting problem, that is it's undecidable and there can't exist a program that does this.

Citra is a 3DS emulator, this is a DS one, how are you comparing them?

Hey, I switched to Firefox because I liked its UI better (after Quantum though)

Zig is "c", but modern and safe.

Zig is safer than C, but not on a level that is comparable to Rust, so it lacks its biggest selling point. Unfortunately just being a more modern language is not enough to sell it.

So imagine if trying to fit in a C-like cousin failed

C++ was not added to Linux because Linus Torvalds thought it was an horrible language, not because it was not possible to integrate in the kernel.

The comparison with Discord makes non sense, the feature seems to be just a normal group chat, like the ones in Telegram/Whatsapp/iMessage. Discord's killer feature is the ability to have multiple channels within a server, which allows more organization.

The only options you have are:

• Dazn Standard (45€/month, 35€/month if you pay for 12 months) to get access to all the SerieA matches (and a whole bunch of other sports nobody cares about)

• Dazn Goal Pass (20€/month, 14€/month if you pay for 12 months) to get access to 3 SerieA matches per week which you don't get to choose (and a bunch of other sports nobody cares about)

• Sky (16€/month for the first 18 months, then whatever Sky wants after that) to get access to 3 SerieA matches per week which you don't get to choose (and a bunch of other stuff nobody cares about)

Most people care only about some specific matches, so your only option is Dazn.

Dazn is also a very crappy service, it often has connectivity problems and also has ads. Fun fact, if you get a connection issue while watching a Dazn ad, it will restart.

So, as usual, monopoly, high costs and crappy services drive piracy.

Sounds like a second password then.

Epic chose not to try and compete with Steam on that front

Forget competing, they lack even the basics.

Note that Rust does not "solve" memory management for you, it just checks whether yours is memory safe. Initially you might rely on the borrow checker for those checks, but as you become more and more used to Rust you'll start to anticipate it and write code that already safisfies it. So ultimately you'll still learn how to safely deal with memory management, just in a different way.

I did that a couple of times, but it was more like "I don't want to grind all of this stuff, I want to skip to the fun part". Also, it's morally different because it impacts nobody else.

A slightly better metric to train it on would be chances of survival/years of life saved thanks to the transplant. However those also suffer from human bias due to the past decisions that influenced who got a transpant and thus what data we were able to gather.