Guessing you mean in a similar vein to the connection between various degrees and food service jobs?

Personally, I’ve been able to avoid IT jobs so far.

Computer science is not IT. IT is about knowing how to use, deploy, and administer existing software solutions, along with a bit of light development to get things to work together when they aren’t necessarily directly compatible.

CS is about creating software solutions and understanding how the pieces fit together (at a low level), as well as how to evaluate algorithms and approach problem solving.

It’s not even coding, though coding is obviously involved. For a coding class, they’ll teach you the language and give problems to help learn that language. For CS classes, they might not care what language you use, or they might tell you to use specific ones and expect you to learn it on your own time. The languages are just tools through which you learn the CS concepts.

An IT professional might know about kernel features and how they relate to overall performance. A coder might be aware that there is a kernel doing OS stuff under the hood. A computer scientist might know the specifics of various parts of what a kernel does and how one is implemented, perhaps they’ve even implemented one themselves for a class (I have, though I was personally interested in that kind of thing and it was for a class notorious for being difficult, so most grads didn’t).

Blizzard used a cheat detection system in wow that allowed their server to send arbitrary code for clients to run. The code failing to return an expected result was a sign that there was tampering going on. Emulating windows api to run on Linux is a form of tampering, though obviously not necessarily a sign of cheating. Guessing they used some code that didn’t work on Linux and banned everyone who failed before realizing that some failed due to Linux, and then were able to separate the Linux users from detected cheaters by how it failed (either that or they had to undo all bans from that round).

Though it does make me wonder if it meant they can’t/don’t detect cheaters on Linux. Probably not, because my guess is they start out by looking for any cheats they can find, install them on test machines, then work at detecting the differences between those test machines and ones without the cheat. So they’d know about Linux-based cheats, too. They might even be able to use timing-based attacks to detect kernel level ones, too.

Can’t they just offer access to your data back at a discounted rate compared to what they charge their data partners for it?

I’m not sure which of the subgroups of this is more frustrating: the ones who refuse to put the necesarry thought towards understanding it but would be able to do so if they did, or the ones who do try their best but still can’t figure out such simple instructions.