is this any good for python ?
The python plugin is excellent. Intellisense and debugging are top-notch. I absolutely love it.
Visual Studio Code 1.8
151–160 of 197 posts
Re: Visual Studio Code 1.8
#152Earlier quoted context omitted.
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.
Neither did I. When I first opened VSCode, I thought it wanted to tell me about something important going on. Maybe color coded an update message or something like that.
Re: Visual Studio Code 1.8
#153I 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
Visual Studio Code itself doesn't either.
Re: Visual Studio Code 1.8
#154How do VSCode features get ported to the Monaco Code Editor[1]? I was interested in using it but noticed the last commit for Monaco was in October. [1] https://github.com/Microsoft/monaco-editor
the monaco editor code is part of vscode. They do a scripted copy to the repository every now and then. Definitely file an issue if its a bit too old.
We usually update the Monaco Editor npm bits shortly after the monthly VS Code release. So this is still on our list.
Re: Visual Studio Code 1.8
#155Why 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…
Not saying Electron is the pinnacle of performance, but IntelliJ and the whole Java Swing stack is just abysmal in my experience. I much prefer VS Code, it feels way 'snappier'.
Re: Visual Studio Code 1.8
#156Earlier quoted context omitted.
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…
>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.
Some of the best programmers advocate for printf over debuggers...
And some of the crappiest programmers run around the debugger for hours with no idea what could be wrong in the program, stepping blindly here and there...
Re: Visual Studio Code 1.8
#157Earlier 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?
If you create a new file, when pressing save, you get a save dialog. In there you can navigate to the folder where you want to save the file.
Re: Visual Studio Code 1.8
#158mini-map is the only thing stopping me from jumping to VSCode.
And a git diff gutter which also displays the original code when hovered. Ever since I started using them I almost literally can't write code without it.
Re: Visual Studio Code 1.8
#159Why 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 j…
Make sure to run PHPStorm with 64-bit Java on Windows if you are on 64-bit platform. Much better experience.
PHPStorm on Windows ships with 32-bit Java. You have to install 64-bit Java yourself and change your Windows shortcut to point to the 64-bit PHPStorm exe. It also has it own vmoptions file.
If you install Jetbrains Toolbox App you can tell that run 64-bit for you and also set java heap size.
Re: Visual Studio Code 1.8
#160Has anyone been able to get decent JS Intellisense working on VS Code? I recently switched to (and decided to pay for) WebStorm, despite the fact that it's debugging experience is slower, because it will properly inspect my project, automatically get the typings .tsd's for all of my node_modules and Node core and put them somewhere out of my way (i.e. not in my project root directory!).
I can then properly refactor my code. I can 'go to definition' and it actually works! Also the editor automatically telling me a 'variable is unused' being switched on by default without some plugin? This should be standard.
Having been a C++ and Java dev before this Node gig, these things were essential for me.
This and the fact that it has lots of tools built in persuaded me to make the switch.
I still keep an eye on the VS Code releases hoping one day I can hop back.