In my opinion the underlying outrage isn't about this pull request in particular, it's about a failure to allow simple customizations like changing interface font sizes from otherwise hardcoded values. [1] It's a usability and potentially accessibility issue, not an aesthetics issue.
In no way was this pull request intentionally targetting compatibility with this extension. But adding exactly this and similar customizations has been requested since 2015 [2] and the requests are either ignored or dismissed, not out of malice. I understand the frustration of feedback being ignored and having to deal with UI or compatibility breaking changes for the sake of some improvement without clear impact. User customizable UI/UX is worth an extra few seconds loading time, in my opinion and the only option is downgrading. Some other people seem to agree and have similarly chosen to downgrade (15 thumbs up in that locked pull request thread). Title is wrongly sensationalized.
Comments
In my opinion the underlying outrage isn't about this pull request in particular, it's about a failure to allow simple customizations like changing interface font sizes from otherwise hardcoded values. [1] It's a usability and potentially accessibility issue, not an aesthetics issue.
In no way was this pull request intentionally targetting compatibility with this extension. But adding exactly this and similar customizations has been requested since 2015 [2] and the requests are either ignored or dismissed, not out of malice. I understand the frustration of feedback being ignored and having to deal with UI or compatibility breaking changes for the sake of some improvement without clear impact. User customizable UI/UX is worth an extra few seconds loading time, in my opinion and the only option is downgrading. Some other people seem to agree and have similarly chosen to downgrade (15 thumbs up in that locked pull request thread). Title is wrongly sensationalized.
1. https://marketplace.visualstudio.com/items?itemName=iocave.c...
2. https://github.com/microsoft/vscode/issues/519