At least it appears to be something that gets triggered. In theory, if a node is not under attack or heavy usage, this isn’t a consideration. Doesn’t seem to be a perfect solution as it still slows the traffic of legitimate users in the event of an attack. I don’t know the full details, but in the worse case it makes it easier to semi-DoS, maybe not by fully making a node unresponsive, but by making the service so painfully slow that users may give up on it.

There are several reserved names in Windows. This is for backwards compatibility with mostly DOS programs. On your desktop, try and create a folder named “con”, and Windows should flat-out refuse. (Same thing for “prn”, “aux” and “nul”)

Adding even more grammar, you could use “Had no”, for lack of possession, like

It had no tooling for the fs?

Accounting details, sensitive credentials for sys admin use, HIPAA data, PII etc. there’s just so much crap understood to be temporarily unlocked, viewed, and then immediately deleted or locked again. Even home users shouldn’t turn this thing on, check your bank? Balance and account details now always available. Use a password manager? Whatever you looked at is likely captured.

Had something similar happen with indiegala. Had an account with them for years, then one day, could not purchase some games randomly. Hit up their support and got the answer “Oh, the purchase was denied because your account’s email address is detected as a temporary email address”… The email address I’ve been using on that account… for years… Is temporary.

The short answer is Rust was built with safety in mind. The longer answer is C was built mostly to abstract from assembly without much thought to safety. In C, if you want to use an array, you must manually request a chunk of memory, check to make sure you are writing within the bounds of your array, and free up the memory used by your array when completely done using it. If you do not do those steps correctly, you could write to a null pointer, cause a buffer overflow error, a use-after-free error, or memory leak depending on what step was forgotten or done out of order. In Rust, the compiler keeps track of when variables are used through a borrowing system. With this borrowing system the Rust compiler requests and frees memory safely. It also checks array bounds at run-time without a programmer explicitly needing to code it in. Several high-level languages have alot of these safety features too. C# for example, can make sure objects are not freed until they fall out of scope, but it does this at run-time with a garbage collector where Rust borrower rules are done at compile-time.

Yeah, I guess. It seems wasteful to need 8GB just to run an OS and browser especially after Microsoft was pushing server core specifically to go the opposite route with resource utilization on servers.

They are necessitating 8GB of RAM. for what?! Like, it would be a struggle to find a machine with less than 8GB still being sold new, sure, but why does the OS need that RAM?