rhombus

Saying an ISA is just a hardware API vastly oversimplifies what an architecture is. There is way more to it than just the instruction set, because you can’t have an instruction set without also defining the numbers and types of registers, the mapping of memory and how the CPU interacts with it, the input/output model for the system, and a bunch of other features like virtual memory, addressing modes etc. Just to give an idea, the ARM reference is 850 pages long.

Having worked at a Target like this, I can assure you there is still a lack of inventory on top of these stores being extremely short staffed. Target in particular completely eliminated their storeroom staff a few years ago and just doubled the work load of the floor staff. Both the floor and the storeroom were absolute nightmares to navigate because there were not enough people to actually organize and stock.

Oxygenated blood is bright red, whereas deoxygenated blood is a darker red. And it looks blue because blue light doesn’t penetrate the skin as deeply as red light. The ones closer to the surface appear blue while deeper ones are purpleish due to the red light reflecting deeper.

It opens the run dialog, which I’m sure the vast majority of Windows users have never heard of. This would trick a lot of people who just trust whatever their computer asks them to do.

It's hard to run any Unity/Unreal game in 4k on my 1070

Both of these engines are capable of making very optimized games, it’s just that most of the developers using them either don’t have the expertise or don’t care to put in the effort.

If a saw sucks ass like the one I used a few days ago, you can't safely cut through wood and you end up doing dangerous things like putting your body weight on the top of the miter saw to get it down all the way, gripping the piece closer to the blade to try to get it to cut better with less tear out or to not slip, etc...

There is a big difference between cheaping out on blades/never replacing them and cheaping out on the saw itself. I agree I wouldn’t get the absolute cheapest miter saw, but a relatively cheap one with good blades that are replaced often shouldn’t be significantly more dangerous than a more expensive one.

That’s fair, I honestly haven’t used it in a while and forgot the real usage of unsafe code. As I said to another comment, it is a really rough language for game dev as it necessitates very different patterns from other languages. Definitely better to learn game dev itself pretty well first in something like C++, then to learn Rust separately before trying game dev in Rust.

Those are fair points. I haven’t used it for a little while and forgot the exact usage of unsafe code. I love Rust, but I totally agree that it’s a rough language for game dev. Especially if you’re trying to migrate an existing project to it since it requires a complete redesign of most systems rather than a straight translation.

The biggest reason is that it's much harder to write prototype code to test out an idea to see if it's feasible and feels/looks good enough. I don't want to be forced to fully plan out my code and deal with borrowing issues before I even have an idea of if this is a good path or not.

There are options for this with Rust. If you wanted to use pure Rust you could always use unsafe to do prototyping and then come back and refactor if you like it. Alternatively you could write bindings for C/C++ and do prototyping that way.

Though, I will say that this process gets easier as you gain more experience with Rust memory management.

Which, again, is an incredibly unlikely attack vector unless you have some government secrets on your computer. And chances are that any attack through the IME or PSP is trying to do an implant into the UEFI/BIOS and not the processor itself.

CPU firmware exploits are incredibly rare, if there even are any that exist beyond proof-of-concept. The chances of getting an infected CPU from this is so unlikely it’s practically impossible.

If I understand it correctly, the chip has the vulnerability, but the malware would be installed on the motherboard in the form of a bootkit. So getting a used CPU is not a threat, but getting a used motherboard is (and kind of always has been) a risk.