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.
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.
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.
It’s because there’s very little they truly believe in, so when they see people on the left have actual convictions they assume they’re liars just like themselves.
Most new EVs have almost as much range as a typical gasoline equivalent, and some can get hundreds of miles of range out of 20 minutes on a DC fast changer. Plus the batteries get an estimated 15-20 years of service, or somewhere between 200,000 and 300,000 miles. That’s around as many miles as a gasoline engine will get before the problems begin piling up.
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.