Live data from Hacker News

Visual Studio Code for Go

github.com

111–120 of 223 posts

Re: Visual Studio Code for Go

#111

Earlier quoted context omitted.

Yeah. VSCode has infinitely more functionality on my macbook than VS does. :D But seriously, if you're running Windows and have a VS license, use VS. Otherwise use VSCode. VSCode is the best IDE for TypeScript. Some will point at atom, they are wrong.

Visual Studio 2015 Community Edition is zero cost and doesn't appear to have any obvious weaknesses (apart from being Windows only): https://www.visualstudio.com/en-us/products/compare-visual-s...

VS Community Edition has licensing restrictions if you're using it at work:

An unlimited number of users within an organization can use Visual Studio Community for the following scenarios: in a classroom learning environment, for academic research, or for contributing to open source projects.

For all other usage scenarios: In non-enterprise organizations, up to five users can use Visual Studio Community. In enterprise organizations (meaning those with >250 PCs or >$1 Million US Dollars in annual revenue), no use is permitted beyond the open source, academic research, and classroom learning environment scenarios described above.

https://www.visualstudio.com/products/visual-studio-communit...

Re: Visual Studio Code for Go

#112
post #52

I like VsCode especially for js css and html5 stuff. The problem I have with it is that it starts to lag when my codebase gets larger eg above 600 lines. Thats the reason why I switch to Atom. I think Atom is the best free text editor.

You may want to take a look at the linters you have installed and in particular the "lint as you type" setting.

Re: Visual Studio Code for Go

#113

Maintainer of the extension here. Happy to answer any questions about VS Code or the Go support specifically.

Hi! I made some Go customizations for atom, and there were a few things that I thought worked pretty well, maybe consider adding them to this project:

1) Auto GOPATH detection: since all code is located underneath a canonical GOPATH, if the GOPATH is not set, traverse upward a few directories until you find one with a "src" folder in it. This means that I don't have to launch it from a terminal and deal with environment variables. Also, I use a GOPATH per project, so as long as each window auto-detects its own GOPATH, that works great.

2) Cross-compile all the tools (gocode, etc) for the most common platforms, presumably windows and mac, and include them in the extension so that it doesn't rely on auto-install or whatever and just works out of the box.

Re: Visual Studio Code for Go

#114
post #21

Earlier quoted context omitted.

I want to start using Visual Studio Code but I am waiting for a VIM emulator plugin that is "good enough" have you tried any of them?

While I'm far from a vim pro, I've never found a vim plugin that didn't frustrate me. Hence I've been stuck in vim because my brain just can't get used to non-modal editing. Just heard from a coworker after I posted this he's switching back to vim because the vim plugin for VS Code isn't quite there.

Visual Studio != Visual Studio Code, but VsVim for Visual Studio is excellent, and this is from a daily/advanced Vim user.

Re: Visual Studio Code for Go

#115
post #73

Earlier quoted context omitted.

Has VS Code still the phone home feature, that can't be turned off? (no it's not okay to sniff on my data or usage, on my computer!)

If you build from source, osscode will never connect to those endpoints. Alternatively, you can just edit them out of the product.json from the release build that you download from MS.

Or just not use this crappy product

Re: Visual Studio Code for Go

#116

Visual Studio Code is my favorite editor. I've mentioned it before but I wanted to add that I'm working on a PHP project and by using XDebug on a local server and VSCode as an editor/debugger I have a really nice lightweight debugging solution. The PHP extension to VSCode is solid.

Is that all fully/smoothly integrated into VSCode? Along the lines of setting a breakpoint in PHP Storm and waiting for it to light up when it's hit? If so, that's sweet.

Yes, yes it is sweet. Set a breakpoint in VSCode editor, run, inspect some variables in VSCode editor debug panel, stop debugging, fix code, run with debugging again -- everything you would expect from smooth debugging experience.

Re: Visual Studio Code for Go

#117
I've used it on a macbook for a short time for node/javascript development, but found it buggy and had to switch back to sublime. The undo (cmd+z) would occasionally get in a weird state where the undo would happen partially (not all lines or columns?) and the whole history would be screwed, or outright stop doing anything. Few times i had to close the file to get last saved version. Perhaps it's something I was doing wrong but it was enough not to use the product, which was great otherwise! Will try again when I hear of new versions coming out..

Re: Visual Studio Code for Go

#119
post #79

Earlier quoted context omitted.

I guess that's exactly what I don't understand. If I add a 32-bit integer and a 64-bit integer, what other possible result could I be expecting besides a 64 bit integer?

> If I add a 32-bit integer and a 64-bit integer, what other possible result could I be expecting besides a 64 bit integer? A 128-bit integer (if you are adding a 32-bit integer and a 64-bit integer, the smallest power-of-2-bits representation guaranteed not to have an overflow is 128-bits, so its the safest result. Though, I'd agree, not the most likely thing most programmers would intend.)

Good point. As painfully explicit as Rust is at times, I'm actually slightly surprised they didn't go that route. (At least for integer sizes less than 32 bits.)

Re: Visual Studio Code for Go

#120
post #2

I'm going to add the customary "I love this new MS" line here. About 10 years ago a friend of mine offered to make an introduction with her cousin, who was an exec at MS, to see about a job when I got out of college. I said "no way, they're working on such boring and dull stuff there" But after having worked in C# for a few years now (loving the language) and seeing all the open source moves they're making, it seems…

I'm kind of a MS fanboy, but please don't believe their lies: - VS is still not free; the community edition can only be legally used by very small companies with slim revenue - the Xamarin acquisition will turn out to be a slap in the face of developers who want to cross target Android and WP - the desaster of the Metro App API that has been replaced by UWP after being hailed as the future of application development for Windows (for a time, you could develop Windows 8.1 Metro Apps only on Windows 8.1 machine, not a Windows 8 machine)

Anybody doing any non-desktop application development on Windows is shouldering the full risk of obsolescence within 2 year.

I would really, really like a cooperation between Google and Microsoft in the area of the utterly braindead 90ies API of Android development by switching to XAML + C# ... ah, a man can dream!

Post reply on HN