Got very confused by the reading order for a second.

Want to give a shoutout to the tutorial that got me into game dev: ChiliTomatoNoodle - C++ 3D DirectX Programming, A very long tutorial but it really goes deep into the basics of graphics api's and win32, Even though i now use vulkan and wayland the underlying concepts that are explained in the tutorial are still the same.

That was a huge rant, i also don't like the microsoft authenticator so guess what i don't use it, and the issue of your private keys to getting stolen if your pc is hacked has long been solved with password protected keys.

All of these issues pretty much amount to nothing, the standard works and is more secure then passwords, same reason as to why enabling password login on SSH is not recommended.

Assuming they don't just do that anyway

The same was said when the ATGM was invented. Yet the tank survived all the same.

And with APS becoming more and more common i predict we will continue to see tanks on the battlefield.

I do think some of these limitations can be resolved. But it indeed poses a big challenge. You can go to big lenghts with server occlusion checking to prevent wall hacks but under zero trust any game with directional sound already has build in wallhacks.

I mostly speak from experience with my developing my own game which is not an FPS. Previously the client would send "i build on this position". Which could very easily be abused. Which I then changed to "i build with this angle and this distance from the previous node" the client would then already show the newly constructed "ghost" node while the server would check if that construction is valid and then send the real position to all clients. The only thing a player would notice is that with high ping the constructed node would move slightly as it got the definitive position from the server. While being significantly more cheater proof.

I suppose im biased towards this kind of thinking since im not working on a FPS game, what for me might be a simple change is a massive undertaking for other genres.

Well yes the peformance ceraintly hasn't caught up yet to x86 but the strongest riscv cpu on the market as far as I know has 64 cores on 2ghz. More then enough to run a desktop.

What is stopping people from bringing RISC-V to the desktop now? Major distros already support it and you can run x86 programs with box64.

What is not fast enough then?

According to MAL the first short should release tomorrow, really hyped for it.

Never going to be enforceable, microsoft and google will probably cave but if you care about privacy you already don't use their products.

Unless op used grok to make this how is it "their" tool if you use an open source model?

I don't use mint so this might be blatantly incorrect but after a bit of searching on mint's release schedule I would assume gimp 3.0 will arrive with the 22.2 or 22.3 version. With 22.2 expected at middle 2025 and 22.3 at start 2026.