Yea, you encounter this a lot at companies with very old codebases. Don't use "chrono" because we have our own date/time types that were made before chrono even existed. Don't use standard library containers because we have our own containers that date back to before the STL was even stable.
I wonder how many of these (or the Google style guide rules) would make sense for a project starting today from a blank .cpp file. Probably not many of them.
I know, I know, long run does not exists in today's investor dominated scenarios. Code modernization is a fairytale. So far I seen no exception in my limited set of experiences (but with various codebases going back to the early 90's with patchy upgrades here and there, looking like and old coat fixed many many times with diverse size of patches of various materials and colour).
And without a few hundreds of billions of EUR invested _today_ there will still be at least a decade until basic infrastructure will be somewhat on par with current day hyperscalers from the US.
And Office suite wise, it took Google about 15 years of pouring money into Google Docs to be almost as good as the MS offering.
Today, if for political reasons some EU companies will switch to whatever Europe has to offer in terms of cloud computing, they will need to spend a significant amount of money to retool their day to day pipelines and invest into developing or replacing cloud services with alternatives from the new provider or self-host if there is no native offering.
There’s a chance that the current situation will start to resolve itself in 3 years and we go back to normal, however that might look.
Jesus Crist and all the saints!
How bad it was before getting in par with MS then?!
If it is now as bad as MS?