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.<p>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 editing tasks) but I found that I was increasingly having to learn outside tools in order to gain the benefit that IDEs could hand me for "free" (free like a puppy, retraining your fingers takes months).<p>Things I love:<p>- Intellisense is immediately superior to anything I've used in EMACS.<p>- Debugging from my editor. This was available in emacs for C, PHP & Java using GDB or similar but it never made it's way to javascript as far as I can tell.<p>- Goto definition.<p>- Good typescript and Flow integration<p>Things I miss:<p>- IDO Mode (FML I hate Finder for moving through directories)<p>- Creating files with just the keyboard (probably possible but I haven't figured it out yet).<p>- Kill ring<p>- Moving around the code with just a keyboard (ctrl-v and the sort).<p>- Non-intellisense completion. When your caret is at the end of a word, Command-\ in EMACS completes to another word from the same buffer that has the same prefix and continue to swap through words on subsequent presses. Very useful in a dynamic language.
VS Code is, along with Typescript and Vue, one of my favorite things to have entered my world in the past 6 months. They have been rapidly improving VSC and I am exceptionally happy with it.
Why are people using this instead of WebStorm? It seems like:<p>- It a little faster for Typescript (but no better TS features from what I can see).<p>- A lot of people are trying it because it's new, or because they like MS tools.<p>- It's free<p>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).<p>My personal calculus is that WebStorm is so cheap, I would not allow my primary tool to be even 1% worse to save money. Also I like those crazy guys - they have been pushing out features very fast for years now.
Anybody know how many people are on the VSCode team? They're moving so fast in adding useful stuff with very few hiccups...I'm lovin' it.
The Just my Code debugger support, where stepping through callbacks can just skip all the in-between functions handled by third party libs looks fantastic.<p>Especially with await / yield-promise type stuff, I could imagine this will make debugging much nicer.<p>[0] <a href="https://code.visualstudio.com/updates/v1_8#_just-my-code-node-and-node2" rel="nofollow">https://code.visualstudio.com/updates/v1_8#_just-my-code-nod...</a>
Being able to hide the activity bar puts VSCode into a class of editors I could imagine myself using. I tried it a couple of times in the past, and that damned big ass bar of useless icons bugged me too much (I work on a laptop screen 95% of the time, so giving up that much real estate for something I'd rather do with hotkeys is just painful). It sounds silly to dismiss it over such a small UI thing, but well...my screen is small, my eyes are getting older (so even though I have a 4k display, I can't shrink everything down without eye strain), and vim and Atom don't eat up the screen in the same way. So, I use vim and Atom (mostly vim, as old habits die hard). But, will give VSCode another try.
It looks pretty good congratulations to the team.<p>There is an issue though that I find so annoying and I just hope they fix it.<p>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 flicks so I type "o" now I have in the terminal "nanio" and sure enough if I now type the name of the file it edits it.<p>Hope this makes sense, I put up with it because I'm really enjoying the product and the speed of development.<p>Big congratulations to the team.
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.
> JavaScript improvements: IntelliSense for paths in import<p>Does that mean we don't need those extensions anymore?<p>- Path Intellisense: <a href="https://marketplace.visualstudio.com/items?itemName=christian-kohler.path-intellisense" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=christia...</a><p>- NPM Intellisense: <a href="https://marketplace.visualstudio.com/items?itemName=christian-kohler.npm-intellisense" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=christia...</a><p>(I have not updated yet)
Anyone using Visual Studio Code for Rust development? If so, how is it?<p><a href="https://areweideyet.com/" rel="nofollow">https://areweideyet.com/</a><p>Going by feature set alone (plugins included) it appears like a good choice, though I've yet to try it myself.
I really like the improvements to the settings system. It's a lot easier to use now while still keeping it a simple json file!<p>Also, I did not know how much I needed Zen mode in my life.
<p><pre><code> JavaScript Intellisense in HTML
</code></pre>
This is awesome - I was just this week looking at using Vuejs for a new project instead of React, but the lack of Intellisense in "Single File Components" with VSCode was a deal breaker for me, better to stay with JSX. I've used all kinds of things before the associated tooling is really up to par, and it's one of those things I often regret later. At least it's still not too late to revisit the decision!
Still waiting on docblock support or plugin for PHP, then I'm going to give it a shot. Till then I'll stick w/ sublime.<p>Though I've been trying vim again, maybe I'll finally jump into it.. I mean I jumped into Arch linux + i3wm(tiled window manager), moving into the console for everything seems next logical transition toward becoming part computer.
Has 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!).<p>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.<p>Having been a C++ and Java dev before this Node gig, these things were essential for me.<p>This and the fact that it has lots of tools built in persuaded me to make the switch.<p>I still keep an eye on the VS Code releases hoping one day I can hop back.
Worth noticing that VSCode currently have the biggest ever active community on Github <a href="https://github.com/Microsoft/vscode/issues/17125" rel="nofollow">https://github.com/Microsoft/vscode/issues/17125</a><p>Over 1500 people, monthly, contribute to the project!
Is VSCode a good tool for someone that is just starting to learn software development?<p>My plan is to become a front-end developer. I am learning Javascript now, then go back a little and learn more deeply CSS, then make some projects with NodeJS and on and on.<p>I use Notepad++ today and it looks good enough for me. So I wanted to ask more experienced developers: a more powerful tool at this early stage of the learning curve help or confuse?
How do VSCode features get ported to the Monaco Code Editor[1]?<p>I was interested in using it but noticed the last commit for Monaco was in October.<p>[1] <a href="https://github.com/Microsoft/monaco-editor" rel="nofollow">https://github.com/Microsoft/monaco-editor</a>
I do almost 100% js dev these days, and I've been switching back and forth between Sublime and VSCode for the past few months. The one major issue I have with VSCode is lack of completions for strings and words which Intellisense doesn't understand. Sublime's CodeIntel dose an excellent job of picking up all the "words" I've used in open files and saves me a lot of typing and typos.<p>Maybe there's some config I'm unaware of, since VSCode's site does mention "words" as a type of completion, but I've never seen it work for js files.
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.<p>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.
I wonder how much of VS Code's community momentum over Atom is due to TypeScript vs Coffee. Personally, I find code bases with great language tooling easier to jump into.
Is there anyway to get user-defined macros? Sublime and JEdit handle them well and was wondering if there is something coming or a preferred extension?
I've just started using VSCode in my python codecamp where 90% of students use sublime. Between the integrated terminal + git, intellisense, and debugger, my proficiency has gone up considerably since I made the switch.