Good for you! :) btw They are recommending VS Code ? I’ve read that some coders opt for the MIT licensed version, and apparently that IDE is very good : https://vscodium.com though probably a matter of taste and work flow. Some programmers probably will always use Emacs because they are so familiar and skilled with it. I agree on embracing so much closed source software being very bad, in a few years time Google Chrome might be so dominant that Google can “rule” the web.
LSP implementations mostly seem to come with a VS Code plugin primarily, and only sometimes will reference how to use the LSP client in other editors. I mean, it makes sense in a way, since VS Code is sort of the flagship LSP client, and authors can’t exactly support every editor people might use. But I can’t help but see it as being free promotion for Microsoft and creating optics to new developers that VS Code is the best or only editor to use.
I see VSCodium a lot like Chromium. It’s open source with a permissive license, but at it’s core it’s still promoting the product and interests of companies that are bent on control. Last I tried VSCodium I had trouble running some plugins, since they seemed to require the official Microsoft release. Maybe there’s a way around that, but I wasn’t interested in putting in too much effort. :)
And with Microsoft having closed sourced their new Python language server, it just leave a sour taste.
That said, LSP has been amazing!!! I get fairly good language support in Emacs for very little effort now! So that’s one good thing to come of this.
I just wish these companies were ok making a living with open protocols instead of using trickery and lock-in to maximize market capture… but that’s capitalism for ya.
Good for you! :) btw They are recommending VS Code ? I’ve read that some coders opt for the MIT licensed version, and apparently that IDE is very good : https://vscodium.com though probably a matter of taste and work flow. Some programmers probably will always use Emacs because they are so familiar and skilled with it. I agree on embracing so much closed source software being very bad, in a few years time Google Chrome might be so dominant that Google can “rule” the web.
LSP implementations mostly seem to come with a VS Code plugin primarily, and only sometimes will reference how to use the LSP client in other editors. I mean, it makes sense in a way, since VS Code is sort of the flagship LSP client, and authors can’t exactly support every editor people might use. But I can’t help but see it as being free promotion for Microsoft and creating optics to new developers that VS Code is the best or only editor to use.
I see VSCodium a lot like Chromium. It’s open source with a permissive license, but at it’s core it’s still promoting the product and interests of companies that are bent on control. Last I tried VSCodium I had trouble running some plugins, since they seemed to require the official Microsoft release. Maybe there’s a way around that, but I wasn’t interested in putting in too much effort. :) And with Microsoft having closed sourced their new Python language server, it just leave a sour taste.
That said, LSP has been amazing!!! I get fairly good language support in Emacs for very little effort now! So that’s one good thing to come of this.
I just wish these companies were ok making a living with open protocols instead of using trickery and lock-in to maximize market capture… but that’s capitalism for ya.