We are not in a post-anonymous world. People who care can absolutely still remain anonymous, for the time being, with enough effort. However, the number of services we can use is being increasingly cut off by these measures. If the trend continues, then we will soon be in such a world, but we are not there yet.

I hate comments like yours beyond belief. "Oh, I'm so smart. It's too much effort to stay private, so I've accepted that a dystopian surveillance state where every action anyone ever takes is recorded permanently and accessible to anyone is inevitable. Look at these fucking idiots worrying about this issue. Can't they just accept it will happen and shut up?"

It is also worth noting that there is a distinction to be made between government and corporate surveillance. Even if it were possible for state actors to de-anonymize specific targets with reliability (it's not, with sufficient opsec), that is very different from a corporation being able to do it. Once a corporation has your data, they will sell it to anyone and everyone, making your entire life public record for anyone to find with a bit of digging. That is a threat model that is much more likely for Average Joe than being targeted by the government, but it is also a threat which is easier to defeat than that of a state actor. This cynical defeatism is baseless.

> by directly letting people modify the source code (Unreal Engine, Godot).

Unreal is not open source, and while Godot is, I would wager 90% of its users never even look at the source code. It very specifically attracts people who want an easy way to make games without prior expertise.

> Players do not care about that.

Users don't care about much when it comes to software quality, honestly. They accept 20 FPS, slow loading, bug-riddled games that consume +20gb ram and +100gb more disk space than necessary. They may complain about a game if it gets bad enough, but they still buy and play those games. My games are significantly more optimized than most. They aren't perfect, but they don't need to be. They don't even need to be as optimized as I have made them, it's mostly just a point of pride and making the kind of software I want to see in the world. I think the only way you lose a player on technical points is if they literally cannot boot your game, but those issues plague engine games too. I had driver issues myself crashing on boot with an UE5 game two weeks ago.

"Modern games" span a wide range of things. I develop solely 2D games, because I prefer 2D games over 3D games. I think that even today 2D games are more enjoyable than 3D games. That doesn't mean Super Mario Bros. That can mean Europa Universalis IV, it can mean Stardew Valley, it can mean Magic the Gathering Online, it can mean Hollow Knight, it can mean Slay the Spire, it can mean a huge variety of interesting and engaging games, none of which require 3D graphics. 2D games can be as complex as you'd like them to be, far more complex in game logic than a 3D shooter even. The more complex you'd like them to be, the easier it gets to implement them if you understand the primitives you're implementing them with. Imagine trying to optimize your data structures when you don't even know what an int32 is? There are real game developers in the world who don't know even that much. It is a great thing that off-the-shelf game engines provide a level of accessibility to allow anyone to develop games, but they do not represent the pinnacle of what can be achieved in software engineering. They are the exact opposite of it, in fact.

> You simply don't know where the bugs and performance pitfalls are because you haven't encountered them, yet.

What is your point? I profile my games and have detailed logging systems. If I or my users run into performance issues, I address them as I come across them. Understanding my codebase at a low level makes it significantly easier to dig into problems and investigate underlying root causes than anyone on Unity will ever be able to. If you use Unity, you are putting your complete faith that Unity has perfectly optimized X low-level problem away at the engine level. If they haven't, and you run into that issue in your game, you are completely fucked. I love being solely responsible for the defects in my games. That means I can fix them myself. The worst thing in the world in software development is when somebody else's fuck-up becomes your problem, and you can't fix it, so you have to implement some hacky workaround, if you can even figure out why the closed-source engine code you didn't write and can't read is behaving incorrectly to work around it in the first place. Sometimes that still happens anyways -- our hardware-OS stacks are built with tens or hundreds of millions of line of dogshit code, and you can't get around it if you want to create software for platforms people use, but you can at least remove as many dependencies on bad code you have no understanding of as possible.