3 ms·

> 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'v

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

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.