|
Those are also less _critical_/replaceable, though. Up until recently, most companies didn't use cloud-y office things, they used, typically, Microsoft Office 2xxx (ie the non-cloud version). Microsoft's cloud-y Office solution is only 7 years old; while Google's is older, it wasn't taken particularly seriously for a long time. Many companies (actually I would suspect _most_ companies) _still_ use on-prem Office/Sharepoint Server/Exchange Server setups, and Microsoft still sells this stuff (Office 2024 LTSC is the latest one for enterprise, Office 2024 for consumers). As for Github, self-hosted or vendor-hosted GitLab would be the obvious solution (self-hosted Github _is_ a thing, but only for large enterprises IIRC); other GitHub-like things are available. I also suspect that Github in particular, and maybe MS, could, if desired, rework their services such that they didn't actually touch personal data in a form that they could disclose to the US government (which is the core issue here). This could be managed via using a third-party auth service (which typically these sort of services already support for enterprise integrations) and, for the Office-y apps, end-to-end encryption. Replacing AWS and Azure and friends would in many ways be the big problem, especially if all this were to happen quickly (in practice, there'd almost inevitably be a significant grace period if things broke down). There's a big capacity problem there; all of these sorts of services operate basically at capacity, because economically it makes no sense to do anything else. That said, in the doomsday scenario, Amazon et al would presumably end up selling off a lot of data centres in Europe (restricted to only non-personal-data applications, they'd need fewer). |