AVX512 was quite a bit of a mess due to the extreme power consumption and even throttling caused by it. At this point, might as well move part of the workload to the GPU.

It makes sense to charge for them, the upgrades weren’t pulled out of thin air, they were made by people who need a steady income so they can pay bills, eat and pay rent (or taxes, or whatever).

When I was trying to derive it myself, I was trying to protectively map the “frustum trapezoid” to a rectangle while preserving the perceived projected depth, but it seemed impossible to do it.

They could be in any format. Plain (tiled) sprites, or compressed, or even encrypted, so it’s hard to say without looking at the game and inspecting it. What you can do, though, is use an emulator to inspect the VRAM while the game is being played.

But, if you’re a computer creating a file to be read by another computer, why not just export the binary representation of the number? This will skip synthesizing the number *and* skip parsing, saving some resources.

Same!

Turns out Swift has full Unicode support, so I could use it and it would accept, even emoji if I wanted to.

Yes, by default, if you don’t put any license, you have an “all rights reserved” copyright that doesn’t let anyone use it or copy it without your permission. However, I doubt you can disallow forks on GitHub.

It doesn’t stop people from reading your code and learning from it though.

I’d say file A maintains its original guid. Or you could generate a new guid for it.

Depends on if you’re trying to encode the “name”, the “existence” or the “contents” of a file. Maybe it would be better to just hash it and use that hash if possible, but then hashes can clash.

iPhone 😅 I also want to get a Mac eventually, at least those have a more homogeneous hardware.

That’s the advantage of consoles (at least unless they decided to launch Pro/X versions); there’s a single unique hardware where your game is supposed to run.