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

71–80 of 197 posts

Re: Visual Studio Code 1.8

#71

Post by wwalser »

maxxxxx wrote: post #63
miguelrochefort wrote: post #13

Earlier quoted context omitted.

I'm confused. Did javascript people not use a debugger before VS Code?

I am pretty to the javascript/node world. The debugging situation is pretty pathetic in my view. Most people I know use a ton of logging like we did with C/printf 25 years ago.

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 to use node --inspect for newer versions of node or node-inspector for older versions.

One common need that is a sad state of affairs in the Node world is performance tooling. It's available and competent professionals should invest in it once it becomes necessary but is a pain in the ass to setup and run.

Re: Visual Studio Code 1.8

#72

Post by WhitneyLand »

adrianlmm wrote: post #64
WhitneyLand wrote: post #57

Why are people using this instead of WebStorm? It seems like: - It a little faster for Typescript (but no better TS features from what I can see). - A lot of people are trying it because it's new, or because they like MS tools. - It's free On the other hand WebStorm still has more functionality overall, a few less rough edges, and a more standard UI (some people don't like how MS Code doesn't have a tabbed doc UI). M…

Go away Jetbrains.

What does that even mean? People were asking about it in comments so I added information.

Are you accusing me of secretly living in the Czech Republic while hanging out HN to astroturf for WebStorm?

Was there a mistake in the comment?

Or, I hate to even ask, is this some sort of childish fanboy thing?

Re: Visual Studio Code 1.8

#73

Post by [deleted] »

angelofm wrote: post #65

It looks pretty good congratulations to the team. There is an issue though that I find so annoying and I just hope they fix it. I set up the external terminal to git bash on windows and sometimes when I'm deleting commands with the backspace it doesn't really delete the full word, hard to explain but as an example if I type "nani" and then press backspace "nani" stays but I know it has been deleted because it kinda f…

[deleted]

Re: Visual Studio Code 1.8

#74

Post by greyman »

_isus wrote: post #6

Finally, we get hot exit. :)

Isn't just better to enable autosave? (VS Code has that as well). I learned its usefulness from PHPStorm, where it is switched on by default. So I just not explicitly save anymore, it is done automatically and immediately.

Re: Visual Studio Code 1.8

#76

Post by ggregoire »

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…

I love VSCode and Flow but to be honest, the Flow integration could be better (and I'm sure it will be, it's just a matter of time).

There is a bunch of annoying bugs waiting to be fixed, e.g. the one about the imported types [1].

In the other hand, I don't blame the maintainers. The Flow team is a really small team and the VSCode extension is obviously not the priority. :)

If you guys see this message, thanks for the amazing work on Flow!

[1]: https://github.com/flowtype/flow-for-vscode/issues/23

Re: Visual Studio Code 1.8

#77

Post by wwalser »

miguelrochefort wrote: post #13
komali2 wrote: post #12

Earlier quoted context omitted.

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

I'm confused. Did javascript people not use a debugger before VS Code?

I don't know why there are so many non-answers or flat out incorrect answers to your question.

Yes, js devs use debuggers and have for years. Firebug was created and popularized for browser js 10 years ago[1]. Node.js was released 7 years ago, got a debug option one year later using node debugger. It was CLI based and a bit shit. Tools which leveraged Node's debug protocol and Chrome's developer tools (node-inspector) for example were started 5 years ago[2]. Most recently some group associated (maybe on?) the Chrome team started creating a cleaner debug protocol and integrating directly with the Chromium project[3]. That's become the gold standard and is the standard way of debugging for Node 7+[4]. VSCode uses that protocol to offer debugging directly from the editor.

1. https://en.wikipedia.org/wiki/Firebug_(software)

2. https://github.com/node-inspector/node-inspector

3. https://github.com/nodejs/node/pull/9028

4. https://nodejs.org/api/debugger.html

Re: Visual Studio Code 1.8

#78

Post by AYBABTME »

miguelrochefort wrote: post #36
amadeusw wrote: post #21

Earlier quoted context omitted.

It was console.log() all the way

You can't be serious.

printf-debugging is a fine way to debug a ton of cases, especially programs with concurrent components. The process of debugging step by step isn't necessarily superior or faster.

Re: Visual Studio Code 1.8

#79

Post by wwalser »

ggregoire wrote: post #76
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…

I love VSCode and Flow but to be honest, the Flow integration could be better (and I'm sure it will be, it's just a matter of time). There is a bunch of annoying bugs waiting to be fixed, e.g. the one about the imported types [1]. In the other hand, I don't blame the maintainers. The Flow team is a really small team and the VSCode extension is obviously not the priority. :) If you guys see this message, thanks for th…

I tried Flow but ended up using Typescript for my current project. If I were to go hard on Flow I'd probably be using Atom with Nuclide instead of VSCode.

I actually like Flow slightly better but the community created type libs for TypeScript convinced me to go that direction.

Post reply on HN