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

Visual Studio Code 1.8

code.visualstudio.com

Post reply on HN
Print view View original

131–140 of 197 posts

Re: Visual Studio Code 1.8

#131

Post by neovive »

kabes wrote: post #16
komali2 wrote: post #12

Earlier quoted context omitted.

The debugger changed how I code. So much better than any other node debug solutions.

How is it better than the one in IntelliJ/webstorm?

I find them to be very complimentary. I switch between VSCode (for writing, code editing) and PHPStorm (refactoring, debugging). Beyond webdev, VSCode offers excellent Markdown support. With auto-previews, custom styles, and many great extensions, it's worth installing just for the Markdown support alone. https://code.visualstudio.com/docs/languages/markdown

Re: Visual Studio Code 1.8

#134

Post by bitwize »

jordache wrote: post #124
wwalser wrote: post #67

I recently moved from EMACS (after using it for ~10 years & ~6 languages) to VSCode. There are loads of things that I miss but overall it's been a fairly smooth transition. I'm moving because I spend most of my time writing javascript and felt that no combination of emacs modes allowed me to keep up with a proper IDE. Emacs is a tool to learn once and use for a lifetime (and I will continue to use it for other editin…

Emacs doesn't do go to definition? Eeek

Installing tern-mode from MELPA makes M-. for JS work in Emacs.

Re: Visual Studio Code 1.8

#137

Post by hprotagonist »

kej wrote: post #27
hprotagonist wrote: post #14

Excellent. I have high hopes for a sublime-style "whole document" scroll bar in future releases.

It's in progress, see [0] this issue. Scroll to the bottom for an update from a few days ago. [0] https://github.com/Microsoft/vscode/issues/4865

ah, i see a lot has happened since the last time i looked. Can't wait!

Re: Visual Studio Code 1.8

#139

Post by passive »

maxxxxx wrote: post #99
wwalser wrote: post #71

Earlier quoted context omitted.

Using awareness of how to use a debugger is a reasonable interview technique WRT javascript devs. In general, ignorance is not a pejorative but if a candidate walk into an interview claiming to be an expert and I find out that you debug in anger using console log, I'm calling bullshit. They're either very green or too lazy to have investigated the tools available. Jr devs are, obviously, another story. Read up on how…

As usual in this industry there is a whole new generation of devs coming up that have forgotten stuff that has been standard for a long time. Then somebody implements this old stuff for the new tech and people think it's major innovation. I am sure soon somebody will create a node profiler.

Sounds like a profitable model (introducing new devs to best practices).

Re: Visual Studio Code 1.8

#140

Post by wwalser »

jordache wrote: post #124
wwalser wrote: post #67

I recently moved from EMACS (after using it for ~10 years & ~6 languages) to VSCode. There are loads of things that I miss but overall it's been a fairly smooth transition. I'm moving because I spend most of my time writing javascript and felt that no combination of emacs modes allowed me to keep up with a proper IDE. Emacs is a tool to learn once and use for a lifetime (and I will continue to use it for other editin…

Emacs doesn't do go to definition? Eeek

It does for languages where you can find a mode that supports it. I never found one for Javascript. Honestly though, while I like the feature, I never notice that it's not there when I'm using Emacs. I can get around in a JS code base.

The only environment that I've been in where it was critical was large Java projects. I would have been lost without being able to goto def though maven dependencies. Having to read XML to figure out where stuff is would have driven me insane.

Post reply on HN