News for hackers. Stuff that matters.

A comment on Why I wrote 33 VSCode extensions and how I manage them. Parent comment

Re:Why I wrote 33 VSCode extensions and how I manage them by windwake12 on Tuesday November 06, 2018 @04:28AM (#18389514)
Having it built in seems just as likely to be a "bad thing", since that version is "baked" in, there's no alternatives. That's why the extension approach by VS code is so surpreme. I'm sure JetBrains would love to have a similar ecosystem.
[ Parent | on HN ]
Re:Why I wrote 33 VSCode extensions and how I manage them by spdionis on Tuesday November 06, 2018 @05:29AM (#18389794)
JetBrains definitely doesn't want a similar ecosystem and having things that work properly 100% of the time baked in is why people use the IDEs.
[ Parent | on HN ]
Re:Why I wrote 33 VSCode extensions and how I manage them by SmellyGeekBoy on Tuesday November 06, 2018 @05:53AM (#18389892)
JetBrains IDEs have a fairly healthy extension ecosystem in my experience.
[ Parent | on HN ]