undefined | Better HN

0 pointsyears35005y ago0 comments

Well for what it's worth, here is something about VS Code LSP and embrace-extend-extinguish.

https://news.ycombinator.com/item?id=25719338

0 comments

This isn't about LSP but specifically pylance. Let's not confuse the issue.

(Incidentally, I don't even use lsp on Emacs, although I may give it a try).

I think the thing is that pylance is a python LSP. And it's proprietary. So they embraced python LSP, extends it so that the additions are proprietary. And pylance might become the defacto python LSP. Typical EEE. Python is hugely popular, it's everywhere - so even if one hates it, might end up having to use it.

Also the remote extensions are proprietary [1]. This has been discussed on HN before.

[1] https://github.com/VSCodium/vscodium/issues/240

BeetleB5y ago

> So they embraced python LSP

They did not embrace LSP. They invented it. LSP came from MS.

> And pylance might become the defacto python LSP.

Nothing is preventing someone from creating another python LSP that will work with the LSP tools. MS is not unique in this. Jetbrains makes proprietary products that are well embraced by the Python community.

2 more replies

j / k navigate · click thread line to collapse

0 comments

BeetleB5y ago

This isn't about LSP but specifically pylance. Let's not confuse the issue.

(Incidentally, I don't even use lsp on Emacs, although I may give it a try).

years3500OP5y ago

Also the remote extensions are proprietary [1]. This has been discussed on HN before.

[1] https://github.com/VSCodium/vscodium/issues/240

BeetleB5y ago

> So they embraced python LSP

They did not embrace LSP. They invented it. LSP came from MS.

> And pylance might become the defacto python LSP.

2 more replies

j / k navigate · click thread line to collapse