3 ms·

Indeed. And even very intelligent, competent AND benevolent MS employees downplay this: https://twitter.com/bitecode_dev/status/1537357261554733056 https://twi

Indeed. And even very intelligent, competent AND benevolent MS employees downplay this: https://twitter.com/bitecode_dev/status/1537357261554733056 https://twitter.com/bitecode_dev/status/1537357261554733056 Steve cannot see how it will lead to attrition or vendor lock in. It's not that there are no good people at MS, but the internal marketting is strong as well.

toyg 4y ago
"It is difficult to get a man to understand something when his salary depends upon his not understanding it." - Upton Sinclair
Spivak 4y ago
I'm having a hard time finding the flaw with this logic, I use pyright but not pylance every day in Neovim and am not locked in at all. Making "the LSP sever that leverages pyright" closed source sucks but is far from the end of the world. If the complaint is that pyright could eventually become non-OSS well that's true of everything.
- BiteCode_dev 4y ago
  It's about the VSCode ecosystems becoming more and more close source to accomodate the dev env as a service strat while using the FOSS root of vscode for PR that deserved to be underlined.
saghm 4y ago
I can't even see what the reason for making an LSP implementation proprietary would be other than lock-in. The argument seems to be "we make it closed so that it can't connect to other things that are closed", which feels pretty silly. Being closed is bad when other people do it, but good when you do it?
jodrellblank 4y ago
Unhappy that you can't have his work for free, you asked /him/ to hand you an equivalent on a plate. He said no. What's he downplaying?
- BiteCode_dev 4y ago
  I noticed vendor lock in. He answered "we only lock the easy bits", which is already a weird idea. Like saying we are only not transparent on the small spending on our IRS declaration. I then question the easy part by asking, tongue in chick, to tell me how I can do the same with FOSS easily. It's freedom I am talking about, not price. Indeed, the proprietary work in question is available without payment already.

toyg 4y ago

"It is difficult to get a man to understand something when his salary depends upon his not understanding it." - Upton Sinclair

Spivak 4y ago

I'm having a hard time finding the flaw with this logic, I use pyright but not pylance every day in Neovim and am not locked in at all. Making "the LSP sever that leverages pyright" closed source sucks but is far from the end of the world. If the complaint is that pyright could eventually become non-OSS well that's true of everything.

BiteCode_dev 4y ago
It's about the VSCode ecosystems becoming more and more close source to accomodate the dev env as a service strat while using the FOSS root of vscode for PR that deserved to be underlined.

saghm 4y ago

I can't even see what the reason for making an LSP implementation proprietary would be other than lock-in. The argument seems to be "we make it closed so that it can't connect to other things that are closed", which feels pretty silly. Being closed is bad when other people do it, but good when you do it?

jodrellblank 4y ago

Unhappy that you can't have his work for free, you asked /him/ to hand you an equivalent on a plate. He said no. What's he downplaying?

BiteCode_dev 4y ago
I noticed vendor lock in. He answered "we only lock the easy bits", which is already a weird idea. Like saying we are only not transparent on the small spending on our IRS declaration. I then question the easy part by asking, tongue in chick, to tell me how I can do the same with FOSS easily. It's freedom I am talking about, not price. Indeed, the proprietary work in question is available without payment already.