Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Era of Visual Studio Code

blog.robenkleene.com

Post reply on HN
Print view View original

151–160 of 698 posts

Re: The Era of Visual Studio Code

#151

Post by orange8 »

gruez wrote: post #86
andrewstuart wrote: post #21

I'm not a fan of VS Code because everything is a plugin. And plugins are inconsistent, buggy, inconsistently documented, hard to use and find and update and goodness knows who developed them. Plugins can be duplicated, outdated, abandoned and incompatible. But worst of all, a big pile of plugins isn't a consistent integrated product vision. I gave VSCode a solid go, and I had to keep installing plugin after plugin, b…

> I'm not a fan of VS Code because everything is a plugin. Replace "vs code" with "javascript" and "plugin" with "library" and you've just described the javascript ecosystem.

Isn't that the very definition of a programming language eco-system? Or is the point you are making being you do not like eco-systems?

Re: The Era of Visual Studio Code

#152

Post by azangru »

leetrout wrote: post #99
gruez wrote: post #86

Earlier quoted context omitted.

> I'm not a fan of VS Code because everything is a plugin. Replace "vs code" with "javascript" and "plugin" with "library" and you've just described the javascript ecosystem.

Yes. And Gatsby has taken it to the extreme.

Gatsby was everyone's darling just a couple of years ago!

Re: The Era of Visual Studio Code

#153

Post by est31 »

orange8 wrote: post #146
nickjj wrote: post #139

The thing that bugs me about VSCode is it's labeled as open source but a lot of pretty critical and interesting components are closed source so you have no idea what's going on under the hood. Normally that's not too big of a deal (I use plenty of closed source apps), but when it's Microsoft it's hard to trust what they are doing with that data. That and I feel that this promotes vendor lock-in at multiple levels. Ov…

What are some of all these pretty critical and interesting components you mention?

I guess they are referring to the Microsoft provided plugins which are proprietary and their license denies usage with any VS code fork. Personally I've never felt the need to use them, but admittedly, I barely use VS code at all.

Re: The Era of Visual Studio Code

#154

Post by et1337 »

Hardly anything could pull my team and I from VS Code's performant UI, great Git integration, astoundingly fast project-wide file search, etc.

At the same time, the Go language server is the bane of our existence. It's so bad that it often blocks VS Code from saving files for minutes on end. To its credit, VS Code's handling of horribly slow plugins is as good as it possibly could be.

VS Code good, gopls bad.

Re: The Era of Visual Studio Code

#155

Post by city41 »

andrewstuart wrote: post #21

I'm not a fan of VS Code because everything is a plugin. And plugins are inconsistent, buggy, inconsistently documented, hard to use and find and update and goodness knows who developed them. Plugins can be duplicated, outdated, abandoned and incompatible. But worst of all, a big pile of plugins isn't a consistent integrated product vision. I gave VSCode a solid go, and I had to keep installing plugin after plugin, b…

Curious what language/env you tend to work in? I have found that working in JavaScript and TypeScript, I don't really need any plugins when using VS Code. I do install a couple, but none are essential, just some small niceties.

Re: The Era of Visual Studio Code

#156

Post by macinjosh »

If you want a text editor with longevity try vim or emacs. They aren't dependent on the benevolence of a greedy corporation. Over time VSCode _will_ be raided by the bean counters at MS and it will begin to track you, give you ads about MS products, and lock you in to their ecosystem.

I'll never understand why a professional developer would give so much influence over their work to the likes of MS, JetBrains, etc.

Sure vim and emacs aren't the easiest to learn but if you're going to write software for a living it is not worth wasting your time with toys like this.

Re: The Era of Visual Studio Code

#157

Post by orange8 »

est31 wrote: post #153
orange8 wrote: post #146

Earlier quoted context omitted.

What are some of all these pretty critical and interesting components you mention?

I guess they are referring to the Microsoft provided plugins which are proprietary and their license denies usage with any VS code fork. Personally I've never felt the need to use them, but admittedly, I barely use VS code at all.

If I've never heard of those plugins, they cannot be that critical or even interesting.

Re: The Era of Visual Studio Code

#158

Post by yepthatsreality »

voxl wrote: post #147
yepthatsreality wrote: post #118

VS Code is nice for green developers, however I always encourage finding a different editor. This helps encourage exploration, customization, and configuration. You will need to take the training wheels off sometime in your career. Another reason to prefer other editors is they tend to stay out of your way. VS Code tries really hard to make you not even leave the window. Anecdotally, a previous colleague once sold me…

Editor and tooling has been flame bait since vim and emacs and you're just stoking the flames. The idea that VS Code is for "green" development only is flatly false, I've used it to work on and debug GCC, hardly green. The idea you should always be looking for new tooling is also false. If you're a power user of emacs then enjoy it. Consider it your super power, I'm not interested in taking that from you. VS Code is,…

> and you're just stoking the flames.

I think the flames were pre-stoked before I wrote anything.

> The idea that VS Code is for "green" development only is flatly false

I did not say it was for only green developers I said it’s nice for green devs.

> The idea you should always be looking for new tooling is also false.

I also never said it was true. I only said I encourage green developers to eventually seek out a new editor.

Re: The Era of Visual Studio Code

#159

Post by bsder »

barkingcat wrote: post #91
andrewstuart wrote: post #21

I'm not a fan of VS Code because everything is a plugin. And plugins are inconsistent, buggy, inconsistently documented, hard to use and find and update and goodness knows who developed them. Plugins can be duplicated, outdated, abandoned and incompatible. But worst of all, a big pile of plugins isn't a consistent integrated product vision. I gave VSCode a solid go, and I had to keep installing plugin after plugin, b…

You don't need all the plugins. You just need a curated set. And some of the plugins are fantastically high quality. The Microsoft Python one is excellent, as is the Remote development one. I'm a fan of VS Code because in spite of it having a plug in system, there are great plug ins there. And that one single great plugin is all that is needed (for that specific purpose)

> Remote development one.

Careful with the Remote Development plugin. It does NOT have an open source license.

Re: The Era of Visual Studio Code

#160

Post by mirthflat83 »

rock_artist wrote: post #79

There’s one big difference between a text editor and other example apps (Illustrator and Excel). Excel is used widely and even with file portability. Microsoft Office is still what many people are used to. Illustrator, In addition of been being popular. It uses their binary ai file format making it harder to switch from. TextEditors unlike those 2 does plain text. So there’s at least no file lock-in for plain text.

He addresses that on his footnote.
Post reply on HN