While we're at it, a reminder that the most popular extension for VSCode is Python support:
https://marketplace.visualstudio.com/search?target=VSCode&ca...
(full disclosure: I'm one of the people working on that)
Would it be accurate to say that after embracing open source with VS code they're extending it with the proprietary pylance?
I'm not sure what you mean by "extending open source". The classic EEE pattern always referred to specific outside standards or specs being "embraced and extended", like J++ did with J2SE. Pylance doesn't extend anything, nor is it a dependency that can lock anyone in.
Re:Guido van Rossum joins Microsoft
by irrational on Thursday November 12, 2020 @10:47PM
(#25078613)
I don’t know. I work for a fortune 100 company and the corporate IT department is purposefully choosing tools not under MicroSofts control. AWS, bitbucket, Slack, Intellij, etc. And developers are encouraged to use MacBook Pros instead of anything running Windows.
I do as well and it's the opposite. Their sales people seem to have their hooks into the decision makers.
If azure "performance crippled" Mysql is anything to go by they'll probably try to start extinguishing the open source components at some point - either by pushing people to use non open source equivalents or by turning their OSS projects proprietary.
I wouldn't be surprised if they've already roadmapped to end open source development on vscode in 2025-2030. The extensions are already proprietary.
They want a golden path from their developer-facing tools (TypeScript, VS Code, C#) to their monthly services (GitHub, Azure, Teams). They're going to make all of that work together as well as they can so you won't want to look elsewhere.
Frankly, it's ingenious. If it works, the hard-to-monetize value of open-source projects like TypeScript and VS Code will be captured in your monthly Azure bill.