3 ms·
> The VSC Codebase (and functionality contained in it) isn't easily ported into competitor products (the fourth point) while Pylance is fully portable by design
by pritambaral 6y ago
> The VSC Codebase (and functionality contained in it) isn't easily ported into competitor products (the fourth point) while Pylance is fully portable by design (could be incorporated into competitor products instantly!).
Only if you consider the LSP standard (proposed and promulgated by MS themselves, made for and with VS Code) as not part of VS Code. My comment — "All of those reasons ... apply ... to VS Code itself" — includes LSP.
In fact, the only reason you can claim "while Pylance is fully portable by design (could be incorporated into competitor products instantly!)" is because of LSP!
Besides, it's not like competitor IDEs that have taken VS Code's codebase wholesale don't exist. Have a look at https://theia-ide.org/ https://theia-ide.org/ for a start!
- Closi 6y agoThe LSP implementation for VS code is part of VS code OSS. Not all LSP language servers are. Just as the C# runtime can be open source, but not all C# programs are.
- pritambaral 6y ago> The LSP implementation ... See, you're still talking about the code. I am (and have been) talking about _the whole project_. Because this isn't about just the code of Pylance. Open Source doesn't mean simply "show us the source code!". Simply making a portion of your code viewable is not sufficient for one to proclaim they "heart Open Source".
- Closi 6y agoThey made the whole editor open source, not just a portion of code. And there is a closed-source product they have (pylance) which they have developed compatibility for. Pylance is NOT part of VS code - It is compatible with it.