Visual Studio Code 1.4

I&#x27;ve been using VSC as my daily driver for a few months now and it&#x27;s great -- even on nightly builds. The most powerful features is the tasks.json. Once I learned to use it (the docs aren&#x27;t good on it), I was able to utilize it to bring a more cohesive experience across many code bases.<p>I enjoy the fact that it gives an integrated experience and allows community extensions. This is a big change from atom where everything must be cobbled together, hope that it works and will break. My hope is that the MS team will pitch in on the most popular extensions per language and take them to the next level as well.<p>To top it off, it&#x27;s one of the most open development processes I&#x27;ve ever seen. They have a clearly defined roadmap, release schedule and even tell you exactly how they work in the wiki (<a href="https:&#x2F;&#x2F;github.com&#x2F;Microsoft&#x2F;vscode&#x2F;wiki" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Microsoft&#x2F;vscode&#x2F;wiki</a>). It&#x27;s fantastic to see such a large company open up like this.

Still no auto-import on Typescript. The main reason I use Webstorm over VSCode currently.<p>What I am talking about:<p><pre><code> * new Foo| * &lt;Ctrl+Space&gt; * (Automatically inserted by editor top of the file where imports are) import {Foo} from &quot;..&#x2F;relativePath&#x2F;to&#x2F;Foo.ts&quot; * new Foo(param);| </code></pre> Working on a large TS codebase without this is absurd. Webstorm is way ahead of VSCode in this area, including things like multiple named imports like:<p><pre><code> * import {Foo, Bar} from &quot;..&#x2F;..&#x2F;foobar.ts&quot; </code></pre> Additionally, things like refactoring filename that affect the all imports that reference that filename -- not sure if that got added in VSCode recently tho.

I have been trying to use VSCode for languages besides JS, like C# and C++, but I&#x27;ve been getting stuck. There&#x27;s a big opportunity here for someone to write up some brief tutorials on how to use VSCode for other languages. So far, the instructions are basically &quot;Get VSCode. Enable the C++ extension. Enjoy!&quot;<p>That&#x27;s not enough, especially when it comes to setting up debugging, which c&#x27;mon, everyone needs. The json config file for C++ debugging has zero documentation. Until there is some more documentation besides the extensions readme, it&#x27;s going to be a little challenging for new users to pick this up and have a delightful experience.

Thanks to the awesome plugin from Luke Hoban, VSCode has been great for writing Go. The best feature is the integrated debugging. Granted, it still relies on Delve, so you have the associated madness with taming <i>that</i> beast (self signing certs on OS X? Although that appears to gone now with the homebrew package).<p>But just being able to type some code, set a breakpoint, run to it, and inspect some locals makes me so much more productive than the Printf driven debugging that so many masochists still cling to.

I felt bad for Sublime. It would be hard for Sublime to compete with MS&#x27;s free IDE. MS finally decides to take over the open source code editor market. VSC also borrowed many features from Sublime such as its famous integrated package manager and keyboard based shortcuts.

The reason I use it: It&#x27;s the only Editor that supports debugging JS in Firefox with this extension <a href="https:&#x2F;&#x2F;marketplace.visualstudio.com&#x2F;items?itemName=hbenl.vscode-firefox-debug" rel="nofollow">https:&#x2F;&#x2F;marketplace.visualstudio.com&#x2F;items?itemName=hbenl.vs...</a><p>AFAIK the only editor that really supports the Firefox Debugging Protocol so far.

Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I&#x27;d use it extensively.

Visual Studio Code is currently my favorite editor. Fast, informative intellisense, great debugging environment, good git integration, faster than Atom, etc.

Whenever I try a new text editor, I run into a problem: I absolutely love the feature where it auto-completes based on other words in open windows (or other files in the open project). But there&#x27;s no official term for this so I can never tell if a text editor has it.<p>Years ago this used to be called &quot;hippie expand&quot;, but I can&#x27;t figure out a more modern name that is used. Does anyone know what Visual Studio Code calls this feature, and&#x2F;or how to enable it (assuming it even exists?)

Great work on the integrated terminal. I&#x27;be been waiting for this. Might even fire up Windows 10 with Ubuntu shell and see how everything works together.

This editor is also very good to write Golang code.

I&#x27;m sure it&#x27;s a great editor but it&#x27;s, to me at least, a bit weird to have to read a privacy statement for an editor to work out what it&#x27;s actually sending home.<p><a href="https:&#x2F;&#x2F;www.visualstudio.com&#x2F;en-us&#x2F;dn948229" rel="nofollow">https:&#x2F;&#x2F;www.visualstudio.com&#x2F;en-us&#x2F;dn948229</a><p>I guess it&#x27;s open source though so if anyone&#x27;s really bothered they could fork it and take all that stuff out.

What would be some of the cool features that only exist on VSC that Sublime doesn&#x27;t have?

Anyone know how to hide the bug icon from the left bar?<p>Other than that I absolutely love vscode. I use it on osx and linux daily. It really hits the sweet spot for my work flow. Cheers to the team for another great release.

vscode is now my favorite editor when I&#x27;m not dealing with command line(e.g. vi), I used to edit with another light weight editor geany.<p>Thanks for all the efforts to make vscode a great tool.

I recently switched over from a combination of Sublime and Notepad++ to VSC. The only thing I found was Notepad++ opens up files almost instantly and there is still a bit of a noticeable lag with VSC, so when I need to be jumping in and out of different scripts Notepad++ is still my preferred choice, but for actually writing code, VSC is golden.<p>Hopefully I can uninstall Notepad++ in the near future!

VSC rocks. I am on .NET&#x2F;Win platform and I can open and work on the same .NET Core project both on VSC on Mac and VS2015 on Windows.

I tried to use it for C++ development on Linux. A project I&#x27;m working on uses Qt, and I put QT&#x27;s include directories into the configuration file as was described in documentation. I was unable to get autocompletion to work with Qt and after 10 minutes I gave up on it and went back to using Netbeans.

I&#x27;m actually finding myself torn in that VSCode is a Microsoft product that I&#x27;m actually liking. For Unity development it offers a much snappier + cleaner experience than the built in MonoDevelop editor, and as a general text editor it seems more responsive than Atom.

I&#x27;m curious about the note on them having implemented an IME for CJK and Indic character input. I thought an IME was a component of the operating system or a contextual widget that appeared like an onscreen keyboard and was separate from the text editor itself.

&quot;By default, VS Code shows snippets and completion proposals in one widget. This is not always desirable so we added a new configuration setting called editor.snippetSuggestions. To remove snippets from the suggestions widget, set the value to &quot;none&quot;.&quot;<p>Sold me on it.

1.4 still has an odd bug - it can&#x27;t deal with some fonts:<p><pre><code> https:&#x2F;&#x2F;github.com&#x2F;Microsoft&#x2F;vscode&#x2F;issues&#x2F;5537</code></pre>

I&#x27;m not particular about what editor you choose. I&#x27;ve been looking for a good JS IDE. Webstorm is of course the only real player in this space (with an amazing IDE) but it&#x27;s pricey. I&#x27;ve been watching VSCode with great interest. However, every time I try the editor it&#x27;s a huge letdown. Buggy, crashy, shitty and weird interface (they have completely made up their own tabbing&#x2F;splitting paradigm for example, which is buggy and alien compared to existing patterns). It claims to be an IDE but doesn&#x27;t come close. I think that one day VSCode will actually be an IDE, but it&#x27;s been a repeated abject failure to date. Based on the current progression I would avoid it for at least the next year, and then I think its potential will be visible.