Visual Studio Code 1.8 • Hacker News Board

Re: Visual Studio Code 1.8

#101

Post by greyman » Thu, Dec 15, 2016, 12:52 AM UTC

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…

I recently switched from PHPStorm (which I already buy license for) to VS Code, and for me the main problem was Java engine on Windows which PHPStorm runs on. I just didn't have a luck to make it work smooth enough, while my computer is quite strong in and of itself. Those occasional hiccups when the editor or whole IDE just frozen for a few seconds driven me crazy sometimes.

So for me, VS Code is a lot faster, not just a little bit. Also command invocation is faster via F1 key.

Apart from that, VS Code just feel a bit more "modern", for example in the areas:

- git integration is more straightforward, or "just better".

- settings are also better organized, no more browsing various dialogs, everything is in one json file.

Re: Visual Studio Code 1.8

#102

Post by grouchoboy » Thu, Dec 15, 2016, 1:01 AM UTC

brulard wrote: post #61

angry-hacker wrote: post #49

Earlier quoted context omitted.

But what is missing in sublime?

The official download page says "Sublime Text 3 is currently in beta" It's been like that for years. First build is from January 2013, it's almost 4 years already. I don't know what specifically is missing there, I just know I'm not comfortable using beta version (with little hope it will ever come out of beta) of a product for daily work. I see it as even developers don't consider it stable enough.

I think that sublime text 3 beta is like debian testing, they are more solid that some others lts products.

VScode and Atom are constantly receiving new features. So we can say that they are still in beta too.

Beta is just a word.

Re: Visual Studio Code 1.8

#103

Post by redpieintheface » Thu, Dec 15, 2016, 1:06 AM UTC

aivosha wrote: post #95

is this any good for python ?

I've been using it to code and debug python for a few months now, support has been getting better and better. I'd recommend this extension for debugging and extra bells and whistles.

https://marketplace.visualstudio.com/items?itemName=donjayam...

Re: Visual Studio Code 1.8

#104

Post by TheCoreh » Thu, Dec 15, 2016, 1:09 AM UTC

rl3 wrote: post #47

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.

It's decent, but far from perfect. Working are: Intellisense, go to definition, some type information on hover.

Sometimes, however, autocomplete doesn't work. (If the file is too big, or if you use macros, both of which are very common in rust.) I found the type info tooltips to not be super precise. There's no live error checking, or at least I couldn't get it to work. I also couldn't get auto formatting to work, but I didn't try much. (Since I can just do it from the command line, anyway)

I wish it had more documentation-related features.

Haven't really tried debugging yet, but should work fine. (I believe it uses GDB)

Re: Visual Studio Code 1.8

#105

Post by RUG3Y » Thu, Dec 15, 2016, 1:18 AM UTC

I never thought that I'd like a Microsoft product again, but VSCode is really neat and has become my editor of choice.

Re: Visual Studio Code 1.8

#106

Post by lobster_johnson » Thu, Dec 15, 2016, 1:28 AM UTC

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.

Re: Visual Studio Code 1.8

#107

Post by ggregoire » Thu, Dec 15, 2016, 1:32 AM 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…

Hey! I just tried the feature and I've an issue: Intellisense suggests everything, not only paths.

e.g. if I start typing './c', it suggests me every symbol in the current file starting with 'c'.

I would love to have only the paths available in the project (like the "Path Intellisense" extension does).

I will post my feedback on GitHub, in case you don't see this message. :)

Re: Visual Studio Code 1.8

#108

Post by geldan » Thu, Dec 15, 2016, 1:37 AM UTC

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?

It's not better. I'd say that the Jetbrains integrated debugging is superior.

Re: Visual Studio Code 1.8

#109

Post by lowmagnet » Thu, Dec 15, 2016, 1:45 AM UTC

saghm wrote: post #94

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…

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.

Re: Visual Studio Code 1.8

#110

Post by lowmagnet » Thu, Dec 15, 2016, 1:52 AM 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

I never even noticed that it was blue as a branding thing. You can toggle it off with Super-K Z now.