3 ms·

- VSCode is open source, so I'm not sure how that constitutes lock in. Switching text editors is pretty easy. - GitHub has some special things like issues and

by jswny 6y ago

- VSCode is open source, so I'm not sure how that constitutes lock in. Switching text editors is pretty easy. - GitHub has some special things like issues and pull requests but in general you can just switch your origin URL to another Git repository that isn't GitHub and boom you are off GitHub. - NPM you can just point your package.json at any Git repository you want, no need to use the NPM package repo. - VSCode Online: like I said, just use a different online editor. Not too much lock in going on here. Integrations and seamless workflow? Sure. But lock in? No I don't think so.

deleted 6y ago
[deleted]
nindalf 6y ago
> Switching text editors is pretty easy. Not only is it easy, VS Code made it easier than ever. By creating protocols for language and debugger support, they've liberated future text editor developers from having to support every language under the sun. By adding support for the protocol, the new text editor automatically gains support for all languages.
- nal10 6y ago
  If you can live with crappy lagging UI. Since the stupid Windows 10 skin VS code is unusable.
  - majewsky 6y ago
    It looks like you replied to the wrong comment.
- toohotatopic 6y ago
  It's just a funnel. As a strategy, you 'commodify' the resources that you cannot control, especially those that are profitable to your opponents. MS is losing in languages, they don't own the important languages for mobile phones: java, kotlin, swift and objectivec and they have a hard time on the server against go and all the other contenders. With some luck the web remains open and typescript will remain an important language since javascript will keep on being important. The moat for the editor is the plugin shop. We will be able to see how committed they are to being open. At least for now, their Live Share plugin doesn't seem to be available for other editors [1]. It's nice to have easy access to debugging but how do you sell your editor if you don't have all the other productivity features? [1] https://news.ycombinator.com/item?id=23244434 https://news.ycombinator.com/item?id=23244434
- viklove 6y ago
  The same way Slack used to have an IRC bridge, but they shut that down once they were the leading market player. This is literally the Embrace/Extend part of EEE
  - nindalf 6y ago
    Oh? And what’s the play after that? How are they going to shut down the protocol or language servers? Even if they remove support for the protocols, those language and debugging servers still exist. Those servers are controlled by a wide variety of organisations, all of whom are committed to supporting the entire ecosystem of editors. It doesn’t take much to regurgitate “EEE” on an MS article. If you can’t even imagine how the final E works in a specific case, maybe say nothing at all.
    - viklove 6y ago
      They'll just disable support for it in VSCode. Got a brain up there buddy? Or maybe you're just an MS shill.
gary-kim 6y ago
With regards to VS Code, there is some, although I'd say not much, lock-in into specifically the Visual Studio Code version of VS Code. Namely, many of the Microsoft extensions only working on the proprietary Visual Studio Code and not the open source VS Code. That does function to negate some of the no lock in benefit of open source. I don't personally think that Microsoft is attempting EEE here but just bringing up the point that it is, to a certain extent, made hard to fork. - https://github.com/VSCodium/vscodium/blob/master/DOCS.md#proprietary-debugging-tools https://github.com/VSCodium/vscodium/blob/master/DOCS.md#pro... - https://github.com/VSCodium/vscodium/issues/240 https://github.com/VSCodium/vscodium/issues/240

by jswny 6y ago

deleted 6y ago

[deleted]

nindalf 6y ago

> Switching text editors is pretty easy. Not only is it easy, VS Code made it easier than ever. By creating protocols for language and debugger support, they've liberated future text editor developers from having to support every language under the sun. By adding support for the protocol, the new text editor automatically gains support for all languages.

nal10 6y ago
If you can live with crappy lagging UI. Since the stupid Windows 10 skin VS code is unusable.
- majewsky 6y ago
  It looks like you replied to the wrong comment.
toohotatopic 6y ago
It's just a funnel. As a strategy, you 'commodify' the resources that you cannot control, especially those that are profitable to your opponents. MS is losing in languages, they don't own the important languages for mobile phones: java, kotlin, swift and objectivec and they have a hard time on the server against go and all the other contenders. With some luck the web remains open and typescript will remain an important language since javascript will keep on being important. The moat for the editor is the plugin shop. We will be able to see how committed they are to being open. At least for now, their Live Share plugin doesn't seem to be available for other editors [1]. It's nice to have easy access to debugging but how do you sell your editor if you don't have all the other productivity features? [1] https://news.ycombinator.com/item?id=23244434 https://news.ycombinator.com/item?id=23244434
viklove 6y ago
The same way Slack used to have an IRC bridge, but they shut that down once they were the leading market player. This is literally the Embrace/Extend part of EEE
- nindalf 6y ago
  Oh? And what’s the play after that? How are they going to shut down the protocol or language servers? Even if they remove support for the protocols, those language and debugging servers still exist. Those servers are controlled by a wide variety of organisations, all of whom are committed to supporting the entire ecosystem of editors. It doesn’t take much to regurgitate “EEE” on an MS article. If you can’t even imagine how the final E works in a specific case, maybe say nothing at all.
  - viklove 6y ago
    They'll just disable support for it in VSCode. Got a brain up there buddy? Or maybe you're just an MS shill.

gary-kim 6y ago

With regards to VS Code, there is some, although I'd say not much, lock-in into specifically the Visual Studio Code version of VS Code. Namely, many of the Microsoft extensions only working on the proprietary Visual Studio Code and not the open source VS Code. That does function to negate some of the no lock in benefit of open source. I don't personally think that Microsoft is attempting EEE here but just bringing up the point that it is, to a certain extent, made hard to fork. - https://github.com/VSCodium/vscodium/blob/master/DOCS.md#proprietary-debugging-tools https://github.com/VSCodium/vscodium/blob/master/DOCS.md#pro... - https://github.com/VSCodium/vscodium/issues/240 https://github.com/VSCodium/vscodium/issues/240