@pounce
> hasn't been open source until last month
what are you talking about? it's been MIT licensed for years

I don't even know what you mean about "pushing other editors out of the way". last I checked, I can still use vim, notepad++, intellij, ...

@2ck
ha, looks like you fell for it, check this out: https://code.visualstudio.com/docs/supporting/faq#_what-does-built-on-open-source-mean
I work for facebook, which is a client of microsoft because we use vscode. A we depend highly on the proprietary features of vs code, and actually have an explicit license to view the code so we can build on it. Some of these parts have never been open sourced, but the majority were last month, so we're doubting keeping the license.

you *can* use vim, np++, etc. but now most languages are prioritizing making vscode work and nothing else. VS Code pretends to be open with DAP and LSP, but unless you specifically design your plugins to be cross-editor they won't be (have you tried using a vscode debugging program as a DAP adapter and have it work in vim?)

@pounce so, they have some proprietary components and distribute under a non-open source license. I wouldn't say that's disqualifying if it's substantially open code. it doesn't make it a "scourge on humanity" either.

still don't see your point regarding other editors. that all seems like a problem for people who make cross-editor plugins: that's a pretty narrow group, nah?

@2ck it's a problem for anybody who uses a non-vscode text editor, it's a scourge because of the EEE motivation