Iron Oxide. Everyone else is wrong.
Ferrous oxide innit?
Wustite, ferrous oxide, is black. FeO.
Typical rust, usually found as hematite, is Fe2O3 and is red/brown. Also an iron oxide.
Magnetite is also another black iron oxide, Fe3O4.
There are quite a few other flavors of iron and oxygen too.
No. OP meant to type crust which is an inedible handle for pizza. I will die on this hill.
It’s a multiplayer survival game in the vein of Minecraft.
That’s a nice way to put it. I call it more of a Noob Murder Simulator
It’s a 2025 movie, starring Alec Baldwin, that gained notoriety in 2021, when a cinematographer was accidentally killed by a live round fired from a prop-revolver that Alex Baldwin was using.
The bane of Intel CPUs, and a trigger word for C geriatrics.
What is the issue with Intel CPUs? I’m OOTL here.
Some of their 13th and 14th generation CPUs have manufacturing defects that resulted in oxidation. In some use cases (servers and such), failure rates sometimes reached 50%. https://www.youtube.com/watch?v=OVdmK1UGzGs
Back in my day we coded in assembly and we liked it that way!
Programming language like many others It has some fancy borrow checker that makes memory usage get statically analyzed by the compiler, so you dont have to manually manage memory, and the program won’t need a garbage collector
so you dont have to manually manage memory
Not sure how this got upvoted with this glaring mistake. You have to manage memory. The point is that the compiler catches it if you make a memory management mistake, making things like data races, uses after frees, etc. literally impossible (short of intentionally using the
unsafetag).I think it’s debatable whether RAII should be called “memory management”. Whether dealing with Rust or modern C++, you don’t need to “manage” the memory beyond specifying a container that will determine its lifecycle behavior, and then you just let it drop.
You could certainly choose to manage it more granularly than that in Rust or C++, but in the vast majority of cases that would be considered bad practice.
That’s a qualitatively different user experience than C or pre-2011 boostless C++ where you actually need to explicitly delete all your heap allocations and manually keep track of which pointers are still valid. Lumping both under “memory management” makes the term so broad that it almost loses its significance.
Yeah, as I understand, in the terms of language design theory, it is technically still “manual memory management”. But since you don’t end up writing
malloc()andfree(), many refer to it as “semi-automatic” instead, which certainly feels more accurate.
Rust is both a nice programming language, and an obnoxious social movement made of a small minority of Rust programmers who are very loud
oh I don’t consider them obnoxious. I’m from Python-land, they’ve been saving our asses with good tooling lol. the quality of output from the rust ecosystem speaks for itself
uv <3
who are very loud
Most of the “should we or should we not” discourses/dramas I’ve read about were initiated or escalated by the anti-Rust crowd. They seem to be a lot more vocal (not to mention impolite) about their opinions than actual Rust developers.
It’s a brutally competitive and toxic game.
You must be looking for /c/playrust
The very fast map in Call of Duty.
a low level language that has really nice features when compared to c and c++, but honestly i find it difficult to read. probably my lack of experience with it, tho.
Rust is iron oxide, mostly used to make thermite
It’s a type of fungus.
