And even if that would be a reasonable argument it would still be an argument for stopping more migration because otherwise you continue to have new first generations.
As someone who happens to be a descendant of one of the very rare pre-1965 immigrants from the subcontinent, I assure you I am not writing this from the inside of a jail cell.
> it is not said honestly out loud, because it is absolutely insane, and would be rightfully rejected
I don't think not saying it out loud is helping the current policy makers; the right and the far right understood right away this was their biggest point. By not engaging them in the discussion , or engaging with hand wavy trickery, you kinda lose the debate I think.
I hate frontend devs that think of themselves smarter than their users and try to be smart about stuff. Just show me the available states, thank you very much.
If users don't know/understand something, you don't help them by hiding it even further from them. Do your part in educating them by simply exposing them to the concept.
This isn't rocket science, just a switch with three states.
Empower your users! Not make yourself the arbiter of features.
You can do this but if it's too granular (like you have no concept of version compatibility) then it can heavily split your matchmaking.
Plus the headaches of keeping many out of date builds up to date enough to deploy.
Even if you don't care about in game compatibility, all your servers still talk to some centralized data store and that will likely want a single deploy that handles old clients
it is not said honestly out loud, because it is absolutely insane, and would be rightfully rejected.