Comment by jasonfarnon
15 hours ago
"literally no one would be surprised" Microsoft 30 years ago was the gold standard for bending over backwards for backward compatibility. For the proposition that once you have purchased one of their products, you didn't have to maintain any further relationship with the company. This behavior is strictly the new 2010s Apple-like microsoft.
That’s not how it worked. They were indeed awesome at backwards compatibility, but the proposition was NOT some principled mindset about long term ownership. It was that upgrading wouldn’t break what you have, overcoming a major sales objection. I think the proposition is better understood as one about FORWARDS compatibility — Windows was (and is) a brittle, poorly architected mess, and so the idea that anything built on it would stay working as the platform evolved was clearly insane and developers would never be able to keep up, so Microsoft absorbed much of the cost. This was actually something they did quite well — a good analogy here might be the heroic response the USSR had to the Chernobyl catastrophe, in which they skillfully managed a disaster whose scope was possible only through a long tradition of poor decisions — and this deserves recognition.
But the reason I think it’s better to think of it as forwards compatibility is that Microsoft gleefully used file formats as a means of driving the upgrade treadmill. Yes, the upgrade to Office 97 would keep everything working to approximately the same level of reliability you had already resigned yourself to — but by default, the files it kicked out would be unreadable in Office 95. There was Save As and an optional free converter… which tired 90s office workers didn’t know about, or particularly want to think about. In the age of literal floppy disks, the friction this created was a significant motivator for businesses to say “fuck it, fine.” Microsoft’s true genius has always been in knowing that “fuck it, fine” is the only bar they ever had to clear, and that through the power of lock-in and sheer institutional inertia, they can drive that bar deep into the belly of the Earth.
Thus, Azure.
Lol, Microsoft has always had sunset periods. They just weren’t great at remote licensing. They would have totally disabled old versions if they could much earlier.
Adobe was really the pioneer for that.
Yup. Evil is gonna evil.
I may be forced to use MS at work but at home I dont let their software past my router. A buddy of mine stayed for a few days while his place was being fixed. "Hey, why are my updates not happening?" "Oops, I forgot to tell you that all MS servers are inaccessible via the wifi."
I’m trying to understand your threat model. Microsoft software is allowed to access the network and communicate with peers on the internet, with the exception of its source of security updates?
Struggling to see anything but more risk with no benefit with this security posture.
>This behavior is strictly the new 2010s Apple-like microsoft.
Surely you jest.
US v Microsoft, the antitrust case, was decided in 1998. Microsoft has always been a shitty company run by shitty people doing shitty things.
They enjoyed a brief upwell in public relations during the period when they had first seemingly embraced open source with WSL, GitHub, and maybe dotnet core, but it was merely a blip.
Being overtly anti-consumer is baked into Microsoft's DNA. They'll always return to that baseline.
> Microsoft 30 years ago was the gold standard for bending over backwards for backward compatibility
And for reselling you the same office suite every couple of years.
(Full disclosure, I worked there in the 2000s... So if anything I should be biased the other way.)
Right, but if you bought office 2000 it was established that you would get to keep using office 2000 for as long as you wanted
Correct, but my point was if they had taken measures to counteract that nobody would have been surprised.
There are probably still a minority using Office 2000 out there, because it still does everything they need.
4 replies →