Earlier quoted context omitted.
Why didn't MS just contribute to the existing one, instead of writing its own from scratch?
The existing one was an open source Microsoft project. Then they built a new closed-source version as a replacement. To be fair, pylance is orders of magnitude better with regards to performance. But I just don’t get what the reasoning was to make pylance closed source. It’s baffling.
> It’s baffling.
Vendor Lock in? Same reason you can't use the VSCode marketplace of mostly open source extensions on a non-Microsoft build of VSCode or any of the remote work features.