4 ms·
I don't think the relative ease of writing extensions for VSCode can be overlooked. There's a relative explosion of extensions addressing a lot of niche needs f
by mgkimsal 5y ago
I don't think the relative ease of writing extensions for VSCode can be overlooked. There's a relative explosion of extensions addressing a lot of niche needs for various markets. My experience is that many of them aren't terribly good, or were good but are no longer maintained, etc. If/when JB makes it more straightforward to write extensions, there may always be a perception different. VSCode extensions in TypeScript will be easier for many curious folks to address vs Java/Scala-based plugins for JetBrains.
- FranksTV 5y agoYeah but the quality is pretty mixed. A lot have performance problems, and maintenance is spotty.
- mgkimsal 5y agoTouched on that with "My experience is that many of them aren't terribly good, or were good but are no longer maintained, etc" But... I realize now my comment was edited some during writing, and I merged two different directions I was heading in in to one comment, and didn't really finish either direction... You're correct that the quality is mixed at best, and... discovery is a pain. I regularly use phpstorm, and when working with others using vscode, I see they've gone through multiple php plugins for vscode, with varying success, and almost nothing comes close to the built-in functionality with JetBrains. The "live share" aspect of vscode is really nice (and 'codewithme' is OK too) but I've rarely been on a team where people ever paired enough to make it a useful or regular part of work. The 'remote' thing is where vscode has really seemed to rocket ahead in the last year or so (just my own observation from colleagues). I didn't understand the attraction, then... on thinking about it more, I guess I can somewhat understand the attraction, but it's not something I've felt compelled to pursue - it's felt like a step backwards. Maybe that will be something I revisit in 2022...