News for hackers. Stuff that matters.
Re:Visual Studio Code for Go by jamra on Thursday March 03, 2016 @12:33PM (#11218378)
Code completion is not as good. I believe VSC uses gocode. VS 2015 also has a cool new feature that shows you references to each function right above the function declaration. Clicking on the reference count will open a quick jump contextual menu.

I wouldn't compare the two products. VS has a SQL editor. It manages database connections. There is an integrated merge tool that is actually quite good. You have project templates, which I haven't found with VSC (I haven't really looked).

Re:Visual Studio Code for Go by lukehoban on Thursday March 03, 2016 @03:38PM (#11219852)
> VS 2015 also has a cool new feature that shows you references to each function right above the function declaration. Clicking on the reference count will open a quick jump contextual menu.

This feature is actually also available in VS Code[0], though only for C# currently. We should be able to add support for this in Go as well[1].

[0] https://code.visualstudio.com/Docs/editor/editingevolved#_re...

[1] https://github.com/Microsoft/vscode-go/pull/75

Re:Visual Studio Code for Go by SiVal on Thursday March 03, 2016 @05:30PM (#11220568)
Very nice feature. While you're in there tinkering under the hood, how about wiring it up for JavaScript & Python, too? (I'm mostly kidding, because this appears to be exactly the direction you're already heading.)

But PLEASE enable basic drag and drop text editing as soon as you can. Since the 1980s, EVERY text component, text editor, IDE, and word processor Microsoft has ever made has had the basic editing ability to drag a selected bit of text and drop it into a new location, with the maddening exception of VS Code where, when you try to drag your selection, you just lose the selection.

There are multiple requests for this in the feature request section of the VSC website, but unfortunately everybody calls it by a different name, so a single, higher-priority issue that would be suggested to most voters as they look over the top of the list is instead recorded as a bunch of low-priority issues lost down in the weeds, discovered by so few that it keeps getting recreated as a new issue.

Re:Visual Studio Code for Go by jamra on Friday March 04, 2016 @02:07AM (#11222447)
That would be amazing. It's a great way to study an unfamiliar code base. It's a great feature on its own as well.
Re:Visual Studio Code for Go by aninteger on Thursday March 03, 2016 @01:10PM (#11218659)
That cool new feature was actually present in VS2013. VS2015 has even cooler stuff but for sure the reference count existed in VS2013.
Re:Visual Studio Code for Go by jamra on Thursday March 03, 2016 @02:31PM (#11219344)
Thanks for the correction. Can you tell which version I skipped? ;P