It’s not that free radicals are good (they are necessary, but excess free radicals are definitely bad), but more so that there is no solid research to suggest that dietary antioxidants have any effect whatsoever. All the studies that show any beneficial effect have been shown to have major flaws or have not been able to be reproduced consistently.

It’s more complicated than good or bad. High levels/sustained stress are definitely bad, but there’s some research to suggest that short-term oxidative stress is an important trigger for various responses in cells.

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.

It definitely should be illegal as a term for using a product or service. At the absolute minimum we should ban non-mutual arbitration clauses and these bullshit “for any dispute” clauses.

For me, if I’m only a little high while on my meds then I am able to read way faster. It’s like the calming effects of weed + focus from my meds lets me just fly through books. If I get actually high, then my meds don’t seem to have any affect anymore, and I just stare at one paragraph forever.

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.