Visual Studio Code 1.8 • Hacker News Board

Re: Visual Studio Code 1.8

#41

Post by thenewwazoo » Wed, Dec 14, 2016, 10:16 PM UTC

miguelrochefort wrote: post #36

amadeusw wrote: post #21

Earlier quoted context omitted.

It was console.log() all the way

You can't be serious.

I'm not sure why not. AFAIK that's still your only option if you want to debug NodeJS code headlessly.

Re: Visual Studio Code 1.8

#42

Post by KayL » Wed, Dec 14, 2016, 10:18 PM UTC

purephase wrote: post #10

_isus wrote: post #6

Finally, we get hot exit. :)

Agreed. This is my favourite new feature. It didn't hold me back from using it at all, but now I can get rid of my other "scratchpad" editors.

Agreed. And now I hope they could improve the startup speed.

Re: Visual Studio Code 1.8

#43

Post by protomyth » Wed, Dec 14, 2016, 10:18 PM UTC

Is there anyway to get user-defined macros? Sublime and JEdit handle them well and was wondering if there is something coming or a preferred extension?

Re: Visual Studio Code 1.8

#44

Post by netcraft » Wed, Dec 14, 2016, 10:19 PM UTC

mmanfrin wrote: post #8

VS Code is, along with Typescript and Vue, one of my favorite things to have entered my world in the past 6 months. They have been rapidly improving VSC and I am exceptionally happy with it.

Do you use typescript with vue? I had researched it at one point, though admittedly not too far in depth, but came away with a conclusion that vue doesn't lend itself well to types.

Re: Visual Studio Code 1.8

#45

Post by octref » Wed, Dec 14, 2016, 10:25 PM UTC

WA wrote: post #29

earthnail wrote: post #17

I know they're working on styling, but now that the titlebar is black, too (on Mac), I really, really would appreciate if the status bar would blend in, too.

Can't upvote this enough. One dev mentioned in a GitHub issue that the blue color is for branding reasons [1]. This is so absurd, it hurts. That status bar is the most distracting and annoying thing ever. See link for suggestions how to mitigate. I use the tip from the person named sysrpl. VSCode is unusable with that blue color for me. 1: https://github.com/Microsoft/vscode/issues/1884

On the other hand, you can toggle it off by View -> Hide Status Bar.

Re: Visual Studio Code 1.8

#46

Post by mattbierner » Wed, Dec 14, 2016, 10:26 PM UTC

ggregoire wrote: post #33

> JavaScript improvements: IntelliSense for paths in import Does that mean we don't need those extensions anymore? - Path Intellisense: https://marketplace.visualstudio.com/items?itemName=christia... - NPM Intellisense: https://marketplace.visualstudio.com/items?itemName=christia... (I have not updated yet)

It depends on what you need. The new built-in path intellisense only applies to JavaScript and TypeScript files for require or import statements. The path intellisense extension specifically is much more general and offers additional functionality that you may find helpful.

I work on the VSCode team on JS and TS support, so please let us know if you run into any problems with the new path intellisense feature or have ideas on how it could be improved.

Thanks

Re: Visual Studio Code 1.8

#47

Post by rl3 » Wed, Dec 14, 2016, 10:26 PM UTC

Anyone using Visual Studio Code for Rust development? If so, how is it?

https://areweideyet.com/

Going by feature set alone (plugins included) it appears like a good choice, though I've yet to try it myself.

Re: Visual Studio Code 1.8

#48

Post by ggregoire » Wed, Dec 14, 2016, 10:30 PM UTC

mattbierner wrote: post #46

ggregoire wrote: post #33

> JavaScript improvements: IntelliSense for paths in import Does that mean we don't need those extensions anymore? - Path Intellisense: https://marketplace.visualstudio.com/items?itemName=christia... - NPM Intellisense: https://marketplace.visualstudio.com/items?itemName=christia... (I have not updated yet)

It depends on what you need. The new built-in path intellisense only applies to JavaScript and TypeScript files for require or import statements. The path intellisense extension specifically is much more general and offers additional functionality that you may find helpful. I work on the VSCode team on JS and TS support, so please let us know if you run into any problems with the new path intellisense feature or have…

Thanks for the info. :)

Re: Visual Studio Code 1.8

#49

Post by angry-hacker » Wed, Dec 14, 2016, 10:30 PM UTC

brulard wrote: post #37

berdon wrote: post #30

Earlier quoted context omitted.

+1 Now I only hope they add in hot-disk support. Sublime Text 3 checks to see if the currently opened version differs from the file system. If it does, it prompts the user to keep the current version or replace it with the disk version. VS Code just replaces the current version with the disk version and doesn't retain history so you can't undo this. I lost about an hour of work yesterday because I had a file open in…

Sublime's updates are dismal. https://www.sublimetext.com/blog/ I had to switch to Atom just because the development is stagnant. I liked Sublime very much. But it's been 2 years already..

But what is missing in sublime?

Re: Visual Studio Code 1.8

#50

Post by mmanfrin » Wed, Dec 14, 2016, 10:31 PM UTC

netcraft wrote: post #44

mmanfrin wrote: post #8

VS Code is, along with Typescript and Vue, one of my favorite things to have entered my world in the past 6 months. They have been rapidly improving VSC and I am exceptionally happy with it.

Do you use typescript with vue? I had researched it at one point, though admittedly not too far in depth, but came away with a conclusion that vue doesn't lend itself well to types.

Not yet -- I'm using TS for an unrelated project to my Vue projects; but I've read that support is on its way.