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

Visual Studio Code 1.7.1

code.visualstudio.com

Post reply on HN
Print view View original

81–90 of 145 posts

Re: Visual Studio Code 1.7.1

#81

Post by gusmd »

satysin wrote: post #47

I enjoy working in C and C++ (on Windows) using Sublime Text however I am thinking of giving VSCode a proper try. I know many people use VSCode for web related development but MS seem quite serious about improving its support for C and C++. My question is does anyone here use VSCode for C and C++? What is your setup? task files, etc?

I mainly use Visual Studio for C++, and Atom for all other things. I gave VSCode a chance a couple of weeks ago but its code completion was not as smart as on VS (no semantic analysis), so I ended up giving up and going back to my VS + Atom setup.

Since you are already using Sublime, you might like it. It felt polished and nice to work on. An improvement over Atom IMHO.

Re: Visual Studio Code 1.7.1

#82

Post by untoreh »

Touche wrote: post #39
athyuttamre wrote: post #21

Earlier quoted context omitted.

Atom loads plugins in the main thread, whereas VSCode runs them in a background thread. This alone makes a huge difference. More here: https://code.visualstudio.com/docs/extensions/our-approach

Same excuse Firefox used to always make for its slowness; it's extensions fault. In the case of Atom, it's slower without any extensions installed, in my experience.

a simple example: on vscode, opening a file from remote fs does not lock the ui, atom (and sublime) freezes. vscode is pretty concurrent! the only thing somewhat slow seems to be regex matches which are single threaded but I am not sure they lock the ui

Re: Visual Studio Code 1.7.1

#83

Post by untoreh »

jrs95 wrote: post #37
ovao wrote: post #15

Earlier quoted context omitted.

I suspect there's some bandwagonism at play in some of it, but I think the VS Code team has generally applied lessons learned from some of Atom's more obvious performance shortfalls (large file handling, for example, for which support was added very incrementally). In my day-to-day usage I'm not seeing any significant performance differences between Atom and Code, but that may just be a function of my particular use…

If you take a look at your memory usage I think you would find that Atom consumes significantly more memory than VS Code. That's always been the case for me, at least.

the biggest memory footprint is gonna come from language servers I think, so check those.

Re: Visual Studio Code 1.7.1

#84

Post by at-fates-hands »

oblio wrote: post #79
mattmanser wrote: post #42

Earlier quoted context omitted.

I don't get the end game though, what is the strategy? Ultimately, if you end up using Linux .net core + typescript, they seem to be killing off visual studio, IIS, Windows Server, etc. For what? Azure, glorified hosting that might end up a race to the bottom vs AWS & GCE? Selling SQL server licences? I just don't get the strategy. I'm genuinely asking, where is this actually taking them apart from burning a bunch of…

IMO the long term strategy is Enterprise Javascript on one hand and Azure on the other one. Azure is the obvious one. Enterprise Javascript is basically: 1. Javascript is probably the most popular programming language at the moment (or at least top 3). 2. Since the creation of Node Javascript has entered the realm of back end services applications. 3. There's a lot of Javascript being written these days, and those li…

>> There's a lot of Javascript being written these days, and those lines of code will have to be maintained.

Maintained and supported. How many JS libraries have developers jumped on, only to see them die a few years later? Backbone JS is the first that comes to mind.

Everybody was using it, but since then, it's pretty much fallen by the wayside and there is still a ton of Backbone code out there that needs maintaining until those projects can transition to something else.

Having a larger enterprise company maintain a library like Typescript when you know its going to be stable and maintained for some time as opposed to a smaller library where the creator just decides to pack it up and leave everybody hanging just seems like a smarter move to me.

Re: Visual Studio Code 1.7.1

#85

Post by Rapzid »

ksubedi wrote: post #77
timdorr wrote: post #12

Earlier quoted context omitted.

I'm curious why Atom gets so much crap for being an Electron app, whereas VS Code is generally praised for it's speed. Are they doing something significantly different from each other?

VSCode actually uses natively compiled C# codebase for all the processing and only uses Electron for the "View" part. Atom does everything in javascript.

Do you have any references for this? I believe most are of the impression that VSCode run entirely on electron/node; even the editor, Monaco, which is written in JS.

Although, I believe their plugin system would allow plugins to be written in any language.

Re: Visual Studio Code 1.7.1

#86

Post by laacz »

I'm blown by the speed of it, considering it's built upon electron. Since I haven't yet decided to upgrade to sublime3, might just give VS Studio a shot. For serious development I use IDE of choice, but for quick text editing sublime might get replaced with VS Studio.

Re: Visual Studio Code 1.7.1

#87

Post by jhasse »

erikbye wrote: post #75
satysin wrote: post #47

I enjoy working in C and C++ (on Windows) using Sublime Text however I am thinking of giving VSCode a proper try. I know many people use VSCode for web related development but MS seem quite serious about improving its support for C and C++. My question is does anyone here use VSCode for C and C++? What is your setup? task files, etc?

Why use VSCode over Visual Studio for C/C++ when your environment is Windows? If you were on Linux or Mac I would recommend CLion or Qt Creator if you wanted a proper IDE. Or a heavily customized Emacs. But on Windows, I would recommend Visual Studio.

VS Code has some features that normal Visual Studio doesn't have. Like multiple cursors or better Git integration.

Re: Visual Studio Code 1.7.1

#88

Post by erikbye »

jhasse wrote: post #87
erikbye wrote: post #75

Earlier quoted context omitted.

Why use VSCode over Visual Studio for C/C++ when your environment is Windows? If you were on Linux or Mac I would recommend CLion or Qt Creator if you wanted a proper IDE. Or a heavily customized Emacs. But on Windows, I would recommend Visual Studio.

VS Code has some features that normal Visual Studio doesn't have. Like multiple cursors or better Git integration.

Hm, feature wise VS is far ahead.

Not sure exactly how the Git integration is better? In addition to improved Git integration with the more recent VS releases there is also a GitHub extension.

VS also has multi-cursor support, if we are thinking of the same thing... editing more than one line simultaneously?

Besides, these two features you mention seem hardly to be of deciding factor, you would think something like code analysis, profiling, and better debugging (memory window, etc) would be of more importance.

Re: Visual Studio Code 1.7.1

#90

Post by Philipp__ »

fahrradflucht wrote: post #38
Philipp__ wrote: post #6

Welp, looks like last night was sleepless for some people.

In Swiss the day just ended. (The vscode team is partly located there)

I know I am from Europe too, but 1.7 was released and pulled back yesterday (evening), and this noon 1.7.1 was released. :)
Post reply on HN