[duped]

I'm not interested in hypotheticals. In AAA games that you have worked on, concretely what 3rd party code did your servers rely on that would prevent you from distributing either the server itself or sufficient description of the servers' behavior to allow a reimplementation?

And even if we're talking hypotheticals: stupid example. I haven't worked on a backend where the actual server infrastructure wasn't open source, trivial to open source because it was first party, or irrelevant because the only thing that matters would be the API and protocols, which again, trivial to make open.

[dijit]

I don’t care.

Get a job in industry and see for yourself.

I’m not going to break confidentially to sate your ignorance.

[duped]

I'm actively trying to remove my own ignorance of the domain which is why I posed the question! You're not breaking confidentiality by saying "I need X to solve Y problem which is offered by Z and we can't expose even the application layer interfaces." Right now it sounds like you don't have an answer, or even understand the question.

Getting all defensive and not answering it doesn't really help your industry's case here.

[dijit]

So when you told me that games use web tech on the backend, that was you getting rid of your ignorance?

Ok, lets talk about the kinds of things we need.

Networks have latency, so we need to smooth/correct for that.

Our connections need to be authenticated, so we need middleware to handle tokens, because we don’t hand-roll that. On a binary protocol.

Our physics engines are complicated: we don’t usually write our own from scratch; and the server needs physics to simulate the world.

Shall I continue?