Go back a little bit further to another Morgan Freeman movie - Se7en (1995) and a big plot point was that it is unthinkable for big brother to be keeping records of what library books people are checking out. Times sure have changed...
I don't disagree with the advice (especially for long lived tokens), but query parameters are encrypted during transit with https. You still need to worry about server access logs, browser history, etc that might expose the full request url.
It is definitely a new frontier. How do you review a game that isn't reproducible? Similarly how do you do play testing? You don't get the same "shared experience" outside of multiplayer and people experiencing it together. It is taking current generation procedurally generated games to the next step, but where do you find a threshold of "this blob of constraints is _the_ game"?
I'm not saying that video games should be confined to today's paradigms, I'm just happily curious to see what will happen with it.
Or similarly the difference between reading/listening to a foreign language vs. writing/speaking one. Knowing how to read code or learn algorithms or design is different than actually writing it. The difference between the theory and practice.
> "Underlying ideas" means cherry-picking opinions that suit your fancy while ignoring those that don't.
Yes, that is how terminology evolves to not meet a rigid definition that was defined in a different era of best-practice coding beliefs. I'll admit I had trouble mapping the DDD OO concepts from the original book(s) to systems I work on now, but there are more recent resources that use the spirit of DDD, Domain Separation, and Domain Modeling outside of OO contexts. You're right in that there is no single recipe - take the good ideas and practices from DDD and apply it as appropriate.
And if the response is "that's not DDD", well you're fighting uphill against others that have co-opted the buzzword as well.
You can remove JSON fields at the cost of breaking your clients at runtime that expect those fields. Of course the same can happen with any deserialization libraries, but protobufs at least make it more explicit - and you may also be more easily able to track down consumers using older versions.