Live data from Hacker News

Visual Studio Code 1.4

code.visualstudio.com

151–155 of 155 posts

Re: Visual Studio Code 1.4

#151

Earlier quoted context omitted.

Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.

Out of curiosity, how did you get it working for Python? Last time I checked, there's no official Python support. There are some unofficial plugins, but none of them have true Intellisense support for Python. (e.g. a la Pycharm, or even Visual Studio Tools for Python). I know they mentioned they were working in it a few months ago on a HN thread, but I haven't heard anything about it since.

There is a doc page describing the features supported by popular extensions. https://code.visualstudio.com/docs/languages/python

Lots of usage out of the top extension. Not quite to PyCharm level, but getting there.

Re: Visual Studio Code 1.4

#152

I have been trying to use VSCode for languages besides JS, like C# and C++, but I've been getting stuck. There'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 "Get VSCode. Enable the C++ extension. Enjoy!" That's not enough, especially when it comes to setting up debugging, which c'mon, everyone needs. The json conf…

Hi, I'm from the VS Code team. We've tried to address this including for C++ https://code.visualstudio.com/docs/languages/cpp.

Can you confirm that you have seen that doc? I opened an issue on github to address the lack of documentation for C++ debugging. https://github.com/Microsoft/vscppsamples/issues/135

Re: Visual Studio Code 1.4

#153
post #51

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

The plugin that comes closest is "VimStyle", which ironically has the lowest number of installs and ratings out of the top three. I assume that's because it was a bit later to market. However, the top two are garbage.

Hey, I'm one of the authors of https://github.com/VSCodeVim/Vim. I'd love to know how we can make our extension better. Feel free to drop by our slack or drop a GH issue of what you think we're missing.

Re: Visual Studio Code 1.4

#154
post #51

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

The plugin that comes closest is "VimStyle", which ironically has the lowest number of installs and ratings out of the top three. I assume that's because it was a bit later to market. However, the top two are garbage.

I just tried VimStyle and wow you are right. This extension is smooth!

Re: Visual Studio Code 1.4

#155

I felt bad for Sublime. It would be hard for Sublime to compete with MS'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.

Those were not invented by Sublime. Lots of older editors have those things, including TextMate and even GNU Emacs and XEmacs. XEmacs had a package manager since the early 1990s. What Sublime has going for it versus these other editors is ease of use and a much better looking UI. But VS Code has that too, and it's free.

MS just doesn't do anything for free even it appears to be that way at the beginning. It simply tries to woo developers to play in their ecosystem.
Post reply on HN