3 ms·
Really nice of him to spend time on OSS tools for VSCode. On the other hand, I feel like the IDEs lugins can do most of these things for me without plugins. I
by Insanity 8y ago
Really nice of him to spend time on OSS tools for VSCode. On the other hand, I feel like the IDEs lugins can do most of these things for me without plugins.
I feel less need to install plugins for their products. And the one plugin that I use in IntelliJ is something I wrote for fun and which doesn't help at all with development. (It shows a random XKCD comic each time I open a new project.)
But it's nice that there is a free IDE available with a rich ecosystem! As a student, I had to deal with Eclipse / Netbeans which seems to me to have been a worse experience than VSCode is these days.
EDIT: fixed some typos.
- fabiospampinato 8y agoThe flip side of this is that an editor that relies on plugins for many features is kind of forced to have good APIs, or plugins authors wouldn't/couldn't make those plugins.
- Insanity 8y agoThat's a good side-effect indeed! I found it quite easy for IntelliJ as well though. (At work we develop some in-house ones as well though they are for specific use cases).