DNS changes propagate. They just do-so in a pull, not push, way.
It’s accurate to say that a user is waiting for the change to propagate if they are sitting there clicking re-try as they wait for the cascading cache expirations to do their thing.
Years ago MS depended on Windows. It was the profit center. Everything MS did was a moat to sell more seats. Even MS-Exchange was just a ploy to force enterprises to stop deploying any other operating system.
That all changed with Azure.
MS realized they could make billions in Windows or trillions with Azure.
They changed the org structure. Now Azure is at the top and everything else is a moat or a way to draw people to Azure. They changed the sales commission (your multiplier doesn’t kick in unless you’ve sold enough cloud services).
Windows is no longer a profit center. It’s a cost center.
Anything that scares people away from using Windows is a benefit.
Let those other suckers spend money developing operating systems. As long as it runs on a VM in Azure, Microsoft will profit.
Windows being worse and worse isn’t a bug. It’s a feature.
I agree, at this point it seems clear that Windows is not their priority anymore and they're trying to scare its users away. But Windows is so penetrated into everyone's office, industry and home that they shouldn't be allowed by law to just leave it like this.
At first, MS didn’t mind as long as SAMBA only implemented the outdated older protocols.
Then they realized interoperability could make them more money, and they invited him and his team to Redmond for a week of working with MS engineers to understand the latest protocol versions.
Oh wait, no, it was because the EU forced them. https://www.theregister.com/2007/12/21/samba_microsoft_agree...
If you need this for Windows so desperately why aren’t you offering to add support for that platform? It’s open source.
Many advanced Go features start in certain platforms and then expand to others once the kinks are worked out. It’s a common pattern and has many benefits. Why port before its stable?
More and more big customers (especially banks) are requiring this kind of self-inflicted-MITM attack from all their suppliers. Do you want to have customers? Get ready for zscaler!
How do you propose compliance with their exfiltration protection requirements? (And “turn down $ from those customers” is not an answer)
It’s accurate to say that a user is waiting for the change to propagate if they are sitting there clicking re-try as they wait for the cascading cache expirations to do their thing.
reply