That doesn't really excuse its behavior in the video though.
Epic chose not to try and compete with Steam on that front
Forget competing, they lack even the basics.
Have you actually measured a performance impact from RefCell
checks?
Does GNOME really need an app to change the theme?
You can also do what this app does manually. The point is that "themes" are an hack and not officially supported, as such it doesn't make sense to provide an official interface to set them.
KDE plasma has this natively...
Do you mean for global themes, application styles or plasma styles? All application styles I can find either use Kvantum or require you to compile them manually...
while a similar C implementation does not need this fix
No, that implementation also needs the fix. It's just that it was never properly tested, so they thought it was working correctly.
Loop unrolling is not really the speedup, autovectorization is. Loop unrolling does often help with autovectorization, but is not enough, especially with floating point numbers. In fact the accumulation operation you're doing needs to be associative, and floating point numbers addition is not associative (i.e. (x + y) + z
is not always equal to (x + (y + z)
). Hence autovectorizing the code would change the semantics and the compiler is not allowed to do that.
However, how are they sabotaging it working on Linux.
For example they discontinued support for Rocket League on Linux (and Mac) after buying Psyonix.
Citra is a 3DS emulator, this is a DS one, how are you comparing them?
Even if the compiler was available to the public most software doesn't use it, so the benchmark is still not representative of real world performance.
People can only remember a limited number of passwords without resorting to systems or patterns.
People also don't have a backup device though.
I did that a couple of times, but it was more like "I don't want to grind all of this stuff, I want to skip to the fun part". Also, it's morally different because it impacts nobody else.
Note that Rust does not "solve" memory management for you, it just checks whether yours is memory safe. Initially you might rely on the borrow checker for those checks, but as you become more and more used to Rust you'll start to anticipate it and write code that already safisfies it. So ultimately you'll still learn how to safely deal with memory management, just in a different way.