Why I wrote 33 VSCode extensions and how I manage them

Re:Why I wrote 33 VSCode extensions and how I manage them by no_wizard on Monday November 05, 2018 @11:38PM (#18388417)

If I’m being completely honest I just see 33 reasons why I still use JetBrains IDEs. Every single one of these features is baked in with the exception of the templates for directory creation which isn’t user configurable most of the time however in the few cases it isn’t baked in they also have a rich plugin ecosystem

Still worthy the money every time. I have to say though VS Code is still one of the best free editors you can get

None the less. Mad props! I think it’s great that they have a rich extension ecosystem

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by markmark on Tuesday November 06, 2018 @03:55AM (#18389391)

Some would argue VSCode can be lighter because these 33 things aren't baked in for those who don't want them.

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by Bishonen88 on Tuesday November 06, 2018 @03:56AM (#18389396)

You can disable most of the plugins in the jetbrain suite, too.

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by SmellyGeekBoy on Tuesday November 06, 2018 @05:53AM (#18389885)

Also not being Electron apps they're probably more lightweight anyway despite the extra features.

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by mariusmg on Tuesday November 06, 2018 @08:17AM (#18390679)

>they're probably more lightweight anyway

Jetbrains IDEs and lightweight in the same sentence. Notepad++ and Sublime Text are lightweight, Jetbrains IDEs are not...

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by redhale on Tuesday November 06, 2018 @09:51AM (#18391451)

I literally laughed out loud sitting here at my desk. JetBrains IDEs are many things, but "lightweight" is not one of them. Electron does not have a monopoly on bloat.

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by vvillena on Tuesday November 06, 2018 @08:09AM (#18390616)

But they are Java apps. I use IntelliJ daily (for Scala development) and I'm happy with it, but it doesn't feel lightweight or snappy.

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by milesokeefe on Tuesday November 06, 2018 @11:07AM (#18392189)

IntelliJ IDEA is easily the worst performing application I use.

I only use it because of the top class Kotlin support (figures, given JetBrains created it).

I end up regularly toggling Power Save mode on and off to reduce how much my CPU gets blown up. That mode turns off code suggestion, auto-imports, and error detection among other pretty core things.

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by isakkeyten on Tuesday November 06, 2018 @04:28AM (#18389508)

Practice has shown that it's easier to add things than to remove them.

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by Aaargh20318 on Tuesday November 06, 2018 @04:24AM (#18389491)

It could have been if it was a real (native) app.

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by hartator on Tuesday November 06, 2018 @12:49AM (#18388705)

You have a way to auto-create changelogs in JetBrains?

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by makepanic on Tuesday November 06, 2018 @01:31AM (#18388852)

If one uses a specification for defining changes, then you can easily generate changelogs regardless of IDE/editors.

e.g. https://www.conventionalcommits.org/en/v1.0.0-beta.2/ has implementations[1] that generate changelogs and bump package versions.

[1] - https://github.com/conventional-changelog/standard-version

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by fabiospampinato on Tuesday November 06, 2018 @08:54AM (#18390938)

I'd be very surprised if every single feature provided by those extensions is integrated in JetBrains to be honest, if it is I might have picked the wrong editor! I'll definitely look into that, thank you.

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by no_wizard on Tuesday November 06, 2018 @10:19AM (#18391739)

They really are, I know I may have exaggerated mildly perhaps as I know a couple of these features aren’t without a jetbrains plugin however I’d say 27 of them are for sure.

[ Parent | on HN ]

Re:Why I wrote 33 VSCode extensions and how I manage them by Bishonen88 on Tuesday November 06, 2018 @03:44AM (#18389353)

Do you know if there's a plugin for the 'bump' thing, as described in the article?

[ Parent | on HN ]

[dead]

Re:Why I wrote 33 VSCode extensions and how I manage them by Natela on Tuesday November 06, 2018 @06:05AM (#18389948)

VSCode is not Open Source and is spyware too : https://code.visualstudio.com/License/.

It's only open source if you build it yourself from Github

[ Parent | on HN ]

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 ]