pie_flavor

That's not a configuration. There is no way to configure Windows to accept files with colons in them. As well say it's a configuration issue if the software hardcodes the assumption of filesystem case-insensitivity.

This is not true. Scams rely on continuous urgency and want the entire process completed without you ever hanging up the phone, and cooling-off periods routinely break the illusion.

The houses cost more because they are bigger. An American house is typically more than double the size of a British house. Credit allows people of the same means to live better.

It typically required more direct sources of trust. If you were a grocery store, you might let customers you personally knew to be good for it, run up a 'tab' and settle on payday. If you were a bank, you might only lend to rich high-class people. You can find this all around the world today; the US is a standout for credit scoring and for access to credit. When a British person wants to sell their house, it has to happen on the same day that the buyer sells their old house, and the house they're moving into to be sold, and so on in a big same-day daisy-chain, until you hit someone who has enough cash for initial outlay. In Japan, up until very recently, you could expect your boss to need to co-sign your apartment lease (and your landlord to immediately escalate any disagreements to your boss).

Yes, and then in the interim we invented having a hundred trillion dollars in GDP. I prefer having access to credit and so does everyone who owns a credit card. If you own a house, you didn't have its cash value when you bought it; neither your car, nor (most likely) your education. In the days of no borrowing, we solved the problem with ramshackle one-room buildings with dirt floors, handcarts, and the one book whose distributors desperately wanted everyone to have it for free.

You could probably point claude at these release notes and have it need no further instructions.

Rust has been a practical experiment in macros for ten years now. I think it is safe to say the results are in: macros are great, and you just needed to have a better style of macros. Making and using something like `tokio::select!` in C-style macros is miserable, but `tokio::select!` is easy to use and understand in Rust.

OBS explicitly disabled the security feature that would have prevented this attack in a real browser.

Java-the-language blows, but Kotlin does not, and Java-the-platform is on the Pareto frontier of oldest-yet-most-usable open-source ecosystems. I prefer Rust, and the gaps where it doesn't apply, C# fits my use cases better, but Kotlin/JVM is a rock solid development platform.

It has been in the language for fourteen years. What would be the purpose of changing it? And what else would ! in the type position signify?

It's used to do all sorts of things. Rust version probing, bindings generation, precompiling bundled data, etc. The only reason it isn't used to do more is because proc macros do it instead, with an essentially identical execution model and sandboxing situation (ie build scripts in isolation are a red herring).

You can disable rust-analyzer running build scripts.

ABI stability is significantly different in a VM language to a native language, and reified generics necessarily require source compilation. Binary-only development for Rust would be exactly as 'sort of not really' as C++, for exactly the same reasons. (There is also no notion of 'installing' dependencies in Rust, and build-time code being malicious isn't much worse than runtime code being malicious.)

Platform support is a non-issue for every library being discussed. This is an array construction macro, it has nothing to do with what operating system you're running on.