Skip to content

Comment on Microsoft mangles VS Code protected properties to prevent UI customizationparent

Comments

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.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.