Curl author asks Microsoft to remove 'curl' and 'wget' aliases from PowerShell
There is a way to address these things that I&#x27;m surprised they don&#x27;t know about as language designers.<p>For these situations, making a change that breaks people&#x27;s code, you have a run-time compatibility mechanism. A command line switch or environment variable can tell the language implementation &quot;please behave like version N&quot;.<p>Then all changes since N which are backwards incompatible are suppressed. For instance, troublesome commands that were removed make a re-appearance.<p>You can then boldly fix something that is obviously wrong, while still giving any negatively affected users a way to fight any fires.<p>It&#x27;s not a perfect solution but it placates most of the concern of the form &quot;this is a good all-round fix, but it will break things for some unknown numbers of users&quot;.<p>(Users who have to be absolutely sure that their code will work the same way regardless of language interpreter and run-time updates simply have to package their work together with a specific version of those components, and have their code refer to them instead of the standard installation.)