One sad lesson I learned early on in my software career is, for every ethical stand you are willing to take as a developer, there's always some other developer who is willing set aside ethics or has a different set of ethics. Software needs some kind of baseline ethical standard, like a Hippocratic Oath. A line that we "shall not cross."
I remember my first job out of college, I was asked to write code that caused our software to cheat at a certain industry benchmark. I was very junior, but still realized it was wrong. I finally worked up the courage to tell my boss that I had an ethical problem with doing this and wouldn't do it, and to my surprise, he said "Oh, that's fine! We treat software developers well here. I'll just give you a different bug ticket to work on!"
Jim, a few cubicles down from me had no problem writing the benchmark-cheating code. It's kind of futile.
Well, someone develops software for nukes, citizen surveillance systems, fraud schemes and technologies for scamming people out of their retirement savings.
If you consider mechanical and chemical engineering there are also people who develop nerve gas agents (usually deployed against civilians), butterfly mines, cluster munitions and incendiary artillery rounds ready to burn your enemies cities to the ground.
Some anti cheating / piracy software that "arguably works" is pretty tame compared to that.
Anti-cheat and DRM are not the same thing, and having community servers with admins greatly reduces the need for anti-cheat. So does not having rewards for winning other than winning.
Some crazy rose tinted glasses here. Back in the CS 1.6 and CS:S days community admins would only catch straight up rage hacks, most aimbots and triggerbots would fly under the radar unless caught by clientside anti-cheat.
But sure, we can pretend that cheaters don’t matter as long as it’s not blatantly obvious to all other players.
I remember my first job out of college, I was asked to write code that caused our software to cheat at a certain industry benchmark. I was very junior, but still realized it was wrong. I finally worked up the courage to tell my boss that I had an ethical problem with doing this and wouldn't do it, and to my surprise, he said "Oh, that's fine! We treat software developers well here. I'll just give you a different bug ticket to work on!"
Jim, a few cubicles down from me had no problem writing the benchmark-cheating code. It's kind of futile.