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

21–30 of 145 posts

Re: Visual Studio Code 1.7.1

#21

Post by athyuttamre »

timdorr wrote: post #12
Pigo wrote: post #5

Electron is a great framework. I've used the same applications on several OS's, each seemed stable and fully functional.

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?

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

Re: Visual Studio Code 1.7.1

#22

Post by laurentdc »

pavlov wrote: post #19
jagermo wrote: post #2

Can I say that I really like the speed of these updates? The team Microsoft really seems to be invested in this free code editor. And a lot of the features are cool, however I really like: | Help > Keyboard Shortcuts Reference brings up a printable PDF reference sheet of VS Code command keyboard shortcuts. Keep this reference handy and you'll be a VS Code power user in no time.

The team Microsoft really seems to be invested in this free code editor. It's great strategic marketing. Making Visual Studio Code costs a fraction of what Microsoft spent on the Surface RT marketing campaign (as an example), and the benefits to their image are much more powerful and long-lasting. The Microsoft brand has been completely reborn in the eyes of developers over the past few years. The lows of 2007-2010 s…

> It's great strategic marketing.

Yeah, it's clear they're trying to "save face" in front of the open source community and become more developer-friendly (Bash on Windows too).

But I must say, ten years ago when I had to choose between Java and C# for a SCADA project I picked the latter because of the Visual Studio IDE which was already well above the competition (think Eclipse/NetBeans back then).

I'm glad they've brought it back for all open source software.

Re: Visual Studio Code 1.7.1

#23

Post by vvanders »

arkitaip wrote: post #20
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…

The performance difference between Atom and VS Code is very noticeable on low and mid range PCs. Most of us here on HN are very fortunate that we can afford high end PCs that minimizes performances bottlenecks but we should keep in mind that most of the world isn't so fortunate and that good performance still matters.

Yeah, I've been floored at how well VSCode works on my ultrabook.

Re: Visual Studio Code 1.7.1

#24

Post by aswerty »

timdorr wrote: post #12
Pigo wrote: post #5

Electron is a great framework. I've used the same applications on several OS's, each seemed stable and fully functional.

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?

Just a thought but, it might just be that Atom is naturally compared with the likes of Sublime Text or gVim and VS Code is naturally compared with Visual Studio.

Re: Visual Studio Code 1.7.1

#26

Post by svieira »

Noseshine wrote: post #17

I have a question. I'm using WebStorm mostly but I'm not "married" to any particular IDE, I've used others and I switch around relatively easily. I'm doing a slightly different programming style when it comes to types: I don't use "no types" or TypeScript or Flow, but I do use "types", sort of. What I've done is JSDoc the hell out of my code. There is not a variable without a JSDoc or Closure compiler type annotation…

Typescript can actually use the types you provide in JSDoc[1] so you will see benefits simply by using VS Code in most cases.

[1]: https://github.com/Microsoft/TypeScript/wiki/JSDoc-support-i...

Re: Visual Studio Code 1.7.1

#27

Post by zumu »

arkitaip wrote: post #20
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…

The performance difference between Atom and VS Code is very noticeable on low and mid range PCs. Most of us here on HN are very fortunate that we can afford high end PCs that minimizes performances bottlenecks but we should keep in mind that most of the world isn't so fortunate and that good performance still matters.

I've been developing on a chrome book for the past year. I can confirm that vs code runs very smooth, while atom is finicky and just flat out dies on opening large folders/files.

Re: Visual Studio Code 1.7.1

#28

Post by [deleted] »

timdorr wrote: post #12
Pigo wrote: post #5

Electron is a great framework. I've used the same applications on several OS's, each seemed stable and fully functional.

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?

[deleted]

Re: Visual Studio Code 1.7.1

#29

Post by Noseshine »

svieira wrote: post #26
Noseshine wrote: post #17

I have a question. I'm using WebStorm mostly but I'm not "married" to any particular IDE, I've used others and I switch around relatively easily. I'm doing a slightly different programming style when it comes to types: I don't use "no types" or TypeScript or Flow, but I do use "types", sort of. What I've done is JSDoc the hell out of my code. There is not a variable without a JSDoc or Closure compiler type annotation…

Typescript can actually use the types you provide in JSDoc[1] so you will see benefits simply by using VS Code in most cases. [1]: https://github.com/Microsoft/TypeScript/wiki/JSDoc-support-i...

That is interesting, I did not know that.

Still, I don't want to use TypeScript for the reasons I wrote. I'm as minimalist as possible, and I don't want to use a language that changes my code to something else without any gain for me since I can write exactly what I want in ES 2015+ already. So it's just those types, and I could get them from "Flow" too and in that case keep my ES 2015+ code. Yes I know TypeScript is very close to ES 2015+, but I never know when it does change the code unless I look at the transpiled result.

EDIT: Actually, I did know that, looking at that page I remember why I dismissed it:

  > Note any tags not listed explicitly below (such as @typedef, or @constructor) are not yet supported.
But that is something I make heavy use of. It would be really messy if I wasn't able to introduce "custom types" even in my limited "IDE based static type system".

Re: Visual Studio Code 1.7.1

#30

Post by Pigo »

aswerty wrote: post #24
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?

Just a thought but, it might just be that Atom is naturally compared with the likes of Sublime Text or gVim and VS Code is naturally compared with Visual Studio.

This makes a lot of since. It's not going to load as fast as most text editors, as it does a lot more out of the box. And most people using VS Code have spent years of their life waiting for VS to open.
Post reply on HN