Yeah, but in the bottom one, the people are packed infinitely dense, which will probably cause the train to derail, saving infinitely more people.

Hungary has a very low income tax. Hence the high VAT. Denmark has both high VAT and income tax.

Before Microsoft demanded TPM 2.0, you could install the latest version of Windows on extremely old hardware. Easily reaching that 15 years. We had this already. And Windows 11 can easily run without TPM 2.0. Microsoft just has business reasons to demand it. So I don’t see how innovation is slowed down by this.

Why the complicated if statements to check the sign? Just let the number overflow. Would be functionaly the same, and result in much prettier code.

Do they also have lab equipment for in Australia?

Nor any pesky neighbours! Win win!

There is one important note: you won’t get cancer from the Teflon in your pans. You get it from the PFAS used to produce the pans. This means you don’t have to throw out all your pans, as if they were made from lead and asbestos. Just make sure not to buy new ones with Teflon.

I looked it up, and bread has about double the amount of carbs as cooked rice, which is probably what is making bread bad.

Probably a rice-only diet would also be bad for them, but nobody brings them tons and tons of rice, while everyone throws them a ton a bread.

Are you that cheap?

TIL. Thank you!

Huh, I thought that they only filtered your blood when donating plasma, hence the PFAS could simply be returned to you. But I have to admit that I’m far from an expert on this matter.

Either way, we kinda have returned to bloodletting being a reasonable medical approach.

When it comes to PFAS contamination, people have been having decent results by simply donating blood often. Getting it out of the system via blood does help to reduce overall levels in your body.

But how does the Rust compiler do that? What does it actually check? Could I write a compiler in C that does this check on a piece of Rust code?

C is so simplictic, that if I can write a piece of functionality in C, I must understand its inner workings fully. Not just how to use the feature, but how the feature works under the hood.

It is often pointless to actually implement the feature in C, since the feature already has a good implementation (see the Rust compiler for the memory safety). But understanding these features, and being able to mentally think about what it takes in C to implement them, is still helpfull for gaining an understanding of the feature.

I mean, at the end of the day, if you really understand your language of choice, you know that it is jusf a bunch of fancy libraries and compiler tricks of top of C. So in my mind, I’m a fully evolved programmer in a language, when I could write anything I can write in that language in C instead.

I have this experience with a certain type of pedestrian traffic light “button”.

I quote button, because nothing physically moves when you press it. I’m not sure if it registers pressure or heat, but you don’t even feel anything move when you press it.

Usually when you press the button, a red text lights up on the button, telling you to wait. This text gives you feedback that the button registered your press, and the traffic light will schedule a green light for you.

However, sometimes you didn’t press hard enough, and the text doesn’t light up. Simple solution: press harder.

But there is a scenario where it doesn’t matter how hard you press, the button won’t light up. You keep staring at it, while slamming the damn thing with the fury of a Hulk wealding Mjolnir. Still, nothing lights up. The reason: the light instantly went green, so it never needed to light up the text telling you to wait. And all that time slamming your fist on the button, could have been spend crossing the intersection. Instead you have been standing there, looking like a drunk person having a fistfight with an inanimate object.

It is a unitless measure, since you divide income (euro) by price of goods and services (euro).

Considering std::cout should only directly be used when you are too lazy to place breakpoints, I totally get the decision to auto-flush.

I remember a javascript library where the was a function that returned, according to the documentation, “a color”. Did it return an object with 3 fields? Were those fields RGB or some other color scheme? Is it a string encoding a color? What format is that string? None of these questions could be answered without just running the code, and analyzing the object you got back.

Do you mean that programming languages are hard to read/write, or that the languages themselves are poorly designed?

In the former case, I invite you to read machine code. Not assembly, but straight machine code. Just zeros and ones as far as the editor can see. Any popular language is better than that.

In the latter case, I invite you to look at the design of an arbitrary natural language. Weird grammer rules, regional differences, loan words that don’t fit in, etc. No programmming language is worse than that. Although I would argue that Javascript has all of those problems too in some degree.

Simple solution: only allow lower case characters in file names.