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

111–120 of 197 posts

Re: Visual Studio Code 1.8

#111

Post by mmgutz »

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…

vs.code

    - FREE
    - faster
    - source is on github
    - easy to write, fix plugins in javascript
    - javascript intellisense is better
WebStorm is a good product but it doesn't really do anything that much better than vs.code that I would go back to it. Was a long time WebStorm user.

Re: Visual Studio Code 1.8

#112

Post by lowmagnet »

I use VSC for Go stuff and the extension (lead author Luke Hoban) for it is excellent. I haven't gotten debugging working properly yet, but I so rarely need it, it's hard to justify configuring it.

I might have to make a few actions to do it, and I'm too busy being productive with the go toolchain tools so nicely integrated with the extension.

Re: Visual Studio Code 1.8

#113

Post by rayiner »

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…

> - Intellisense is immediately superior to anything I've used in EMACS.

For JS maybe. Irony with irony-clang is the best C++ autocomplete I've found. VSCode's C++ Intellisense is crap.

Re: Visual Studio Code 1.8

#115

Post by wwalser »

lobster_johnson wrote: post #106
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…

Creating files: Command palette -> New file. There's also a new plugin called Advanced New File. For completion: Ctrl-space will force a completion at your current location.

The command palette seems like the sort of thing that'll have more power than I'm currently giving it credit for. How do you create a file outside of the directory that you're currently editing?

Re: Visual Studio Code 1.8

#116

Post by wwalser »

rayiner wrote: post #113
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…

> - Intellisense is immediately superior to anything I've used in EMACS. For JS maybe. Irony with irony-clang is the best C++ autocomplete I've found. VSCode's C++ Intellisense is crap.

I have unfortunately not done much C or C++ development since uni. I know that SLIME always seemed far and away the best lisp editing experience.

Re: Visual Studio Code 1.8

#117

Post by wwalser »

lowmagnet wrote: post #109
saghm wrote: post #94

Earlier quoted context omitted.

Do you use any extension to use emacs keybindings? I've tried out VS Code a couple of times and wasn't able to find an extension for emacs keybindings that had everything I use in it. When I tried out Atom, one of the packages for this worked fairly well (although I have other issues that prevent me from using Atom as my full-time editor)

They just introduced keymap modes, including emacs.

I didn't know this! I just created a few keyboard shortcuts that I commonly use manually. Not perfect but it's gotten me over the hump. I may check out the emacs bindings on a slow day.

Re: Visual Studio Code 1.8

#118

Post by vyrotek »

mmanfrin wrote: post #50
netcraft wrote: post #44

Earlier quoted context omitted.

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.

Is there more work to be done besides the reference made in this announcement?

> vue core, vue-router and vuex 2.0 all have TypeScript typings shipped in the npm packages

https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b...

Re: Visual Studio Code 1.8

#119

Post by lobster_johnson »

wwalser wrote: post #115
lobster_johnson wrote: post #106

Earlier quoted context omitted.

Creating files: Command palette -> New file. There's also a new plugin called Advanced New File. For completion: Ctrl-space will force a completion at your current location.

The command palette seems like the sort of thing that'll have more power than I'm currently giving it credit for. How do you create a file outside of the directory that you're currently editing?

The Advanced New File [1] plugin lets you type a relative file name.

[1] https://github.com/dkundel/vscode-new-file

Re: Visual Studio Code 1.8

#120

Post by nobleach »

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?

Some of us used debuggers way WAY back in 2002. Venkman was the new hotness: https://en.wikipedia.org/wiki/Venkman

Firebug quickly became the defacto later on. But telling your average web designer about breakpoints, stepping over and stepping into would cause their eyes to glaze over.

Post reply on HN