| ▲ | dijit 9 days ago | |||||||||||||||||||||||||||||||||||||||||||
Of the 7 AAA games I’ve been part of making, not a single one used HTTP (well, not as a primary driver of anything), HTML, CSS or anything that could be construed as a “web technology” so, what are you talking about please? | ||||||||||||||||||||||||||||||||||||||||||||
| ▲ | duped 9 days ago | parent [-] | |||||||||||||||||||||||||||||||||||||||||||
s/web/networked computers/g What I'm saying is you have programs running on user machines, and programs running on your machines. There's an interface between those two over a network. There's a problem that consumers face today where they pay to play games that are not functional without data flowing over that interface. There's a claim that implementing the backend side of that interface is so complex and impossible or too difficult/time consuming/etc to design in a way without 3rd party dependencies. I'm asking: what are those 3rd party libraries doing? And why can't you design server APIs and client code in a way to provide a different backend if consumers need to do it themselves when you stop supporting the game? | ||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||