I don't really see the problem? If your extension relies on private properties the onus is on you that it might break at any time without notice. The title is highly misleading as well, the change was made to reduce the bundle size and startup speed, a 5% change is considerable. While I understand the frustration that something that used to work no longer works, I don't really see how Microsoft is supposed to be in the wrong here.
With a sufficient number of users of an API,
it does not matter what you promise in the contract:
all observable behaviors of your system
will be depended on by somebody.
My answer was why Microsoft "might" be wrong here. If you look at the history of Windows, Microsoft has compromised because people have relied on behavior like if the windows version is less than XP allow this software to run. So, they hacked some tricks that windows 7 was also able to run windows XP softwares even those software ran version checks.
The problem here is Microsoft didn't provide customization for "technical" reasons. So, a user had no choice but to rely on private fields because they were truly facing some accessibility issues. I also don't like the way VS Code wastes vertical space. Hence, they also broke my vscode ui. I will personally disable upgrade.
Comments
I don't really see the problem? If your extension relies on private properties the onus is on you that it might break at any time without notice. The title is highly misleading as well, the change was made to reduce the bundle size and startup speed, a 5% change is considerable. While I understand the frustration that something that used to work no longer works, I don't really see how Microsoft is supposed to be in the wrong here.
Here is the Hyrum's Law[1]
With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody.
[1] https://www.hyrumslaw.com/#
That doesn’t mean that every observable behavior needs to be supported or continue.
My answer was why Microsoft "might" be wrong here. If you look at the history of Windows, Microsoft has compromised because people have relied on behavior like if the windows version is less than XP allow this software to run. So, they hacked some tricks that windows 7 was also able to run windows XP softwares even those software ran version checks.
The problem here is Microsoft didn't provide customization for "technical" reasons. So, a user had no choice but to rely on private fields because they were truly facing some accessibility issues. I also don't like the way VS Code wastes vertical space. Hence, they also broke my vscode ui. I will personally disable upgrade.