[BeetleB]

> 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.

[years3500]

> LSP came from MS.

Thanks, today I learned.

Yeah anyone is free to create, same as anyone is free to create remote extensions for VSCodium. So far nobody seems to have done it. Even if somebody does it, it might not match the quality and features of MS extensions.

MS has a history of EEE. Jetbrains doesn't, and as far as I know they are no bullshit no dark patterns high quality.

[BeetleB]

I get where you're coming from. It's just amusing that many people talk about how great it is to use LSP with Emacs, but are simultaneously recommending not to use MS tools :-)

If one is concerned enough not to use VSCode because it is MS, then one should also not use LSP.

[years3500]

LSP is great. The thing about VSCode is dark patterns. VSCode is great, one sees that it's MIT licensed, downloads it uses it and is like wow nice. After a while realises that the official build is not FOSS licensed and contains telemetry code. So one finds 'VSCodium' which is a community port without telemetry. You carry on working but now remote things are not working. One looks why - the only reason is MS made it proprietary. Remote is essential for lots of developers. One feels f*cked by MS. Few years ago, Github's 'Atom' editor was getting popular. Then MS bought GH now Atom reduced to atoms - can't see it anywhere - though getting updated.

[daptaq]

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

I don't think this changes the issue: EEE became CEE (Create, Extend, Extinguish).