>>716031040
LEGALESE CONTRACTS TO OBFUSCATE AND LAMPSHADE SCAM PRACTICES IS LITERALLY ILLEGAL AND IS TESTED IN NOT ONLY EURO COURTS, BUT ALSO AMERICAN COURTS. EULAS ARE ALSO NOT GLOBRABLLY RECOGNIZED AS A CONTRACT.
COME HERE YOU FUCKIN' VTUBER CUNT.

>>716031089
It literally is where I live, sucks to suck.

>>716031097
SEMANTIC FUCKING BULLSHIT WILL PUT YOU ON THE RAPE LIST AS WELL

>>714750138
You utter fucking monkey, by not doing that you are opening yourself up to get RAPED when the third party service goes kaput. They might be great programmers in other parts of the code, but they will eventually leave their company to get buttfucked when the service needs to change for one reason or another, which is always a possibility.

>>714750141
Don't get me fucking started on that side of things. Getting to pierce the veil when it comes to "behind the scenes" code really shows how much of the modern world is running off of open code AND YET THESE FAGGOT CORPS WILL SHIT ON ANYONE WHO FUCKING DARES TO TOUCH THEIR CODE AND THEN AT THE SAME TIME SHIT ON THE PROGRAMMERS THAT MADE THEIR CODE POSSIBLE

>>714661830
>The budget, resources & dedicated development time ARE additional costs,
No it fucking isn't, if you go in designing these things from the start then that's just the cost of the project itself. I highly, highly, highly fucking doubt that performing an offline build, which is necessary for the construction of software in a safe reliable manner to allow for collaborative changes to necessary components before going live. You are going to tell me that you test server capabilities in a live environment? Fucking please. You also trying to get me to believe that you don't design basic as fuck functionality to only be updated alongside microservices depending on their API calls or what they required to be spun up server side? Bitch please.
>And you think the decoupling comes for free? Does QA keep testing for dedicated server capability? Who pays them to do so?
If you designed it from the start with smart server calls and functionality, it shouldn't cost you anything additional since that would be called basic requirements and once you have gotten a procedure or standard, it's easy to transfer those kinds of things into future development. For your first live-service-to-offline game it would be a challenge, but afterwards like you would do with any legacy code base, you would take what you learned to make future projects more efficient, better and standard.
>They make live-service games, of course they're retarded. But you cannot legislate this.
Too bad, the rest of the software industry has to deal with legislation regarding the handling of data, what type of data can be collected and the voluntary opt in nature of data collection, vidya gayme apes should suck it the fuck up.
>I'll take your ad hominem as a concession.
NIGGER, I'm only mad because I'm sick of you monkeys thinking that you are special for being in the games industry or working on SaaS products. You're not, you are a monkey.