I had a good experience overall with this plugin (once it was set up, which wasn't exactly trivial), but it keeps auto-completing in comments so when I hit [return] it inserts some random word rather than going to the next line. Every time I want to go to the next line I have to press [esc] then [return].
Visual Studio Code for Go
11–20 of 223 posts
Re: Visual Studio Code for Go
#12Debug support, syntax highlighter, looks very nice.
Having trouble getting go build on save working.
Re: Visual Studio Code for Go
#13I've found myself always coming back to VSCode for my (stupid simple, nothing crazy like Docker or anything) Go projects.
They've really done a fine job with the editor and extensions. Bravo Microsoft!
Re: Visual Studio Code for Go
#14We're a 100% Go shop and everyone on my team but me uses Visual Studio Code for Go. It's really amazing. (My mind has just been so corrupted by years of vim usage I'm trapped.)
It's bizarre to think my team writes in a language created by Google in an editor created by Microsoft on System76 laptops running Ubuntu. Never would have been possible in the Gates or Ballmer eras.
Re: Visual Studio Code for Go
#15I have been working for sometime with Visual Studio Code and with this Go extension. I used to use Sublime 3 for Go development, but with this extension I have noticed that I use more often vscode than sublime for Go development.
It is also a big plus that vscode works very well with TypeScript and you can work seamlessly with TypeScript front and Go backend code.
One nice thing is that you can navigate e.g. function calls easily, which places call a function or directly find correct function in question like foo.New() by pressing F12 or shift+F12. When using Sublime to navigate to foo.New() would probably reveal quite many functions that are in your workspace path.
Go extension also imports automatically packages that you use in your code. Renaming types or functions also works nicely if your code compiles.
There are certainly things to be improved like not being able to conveniently use directories outside your vscode project e.g. common packages across different projects. But over all developer experience is really nice.
Re: Visual Studio Code for Go
#16Maintainer of the extension here. Happy to answer any questions about VS Code or the Go support specifically.
Re: Visual Studio Code for Go
#17I've never programmed in Go before. Coming from a C# background. Can someone tell me, how does Go feel? Is is pleasant to work in, or is it tricky like C.
It's very pleasant to work in. It has its quirks and language design rigidity and can get tricky, though not quite "like C" unless you're implementing cgo directly.
Re: Visual Studio Code for Go
#18Even if you don't like MS or distrust them, seriously...
VS Code is a very good spiritual successor to TextMate. It has better performance characteristics for me than Atom, and I find extending it much less intimidating than Atom. I'm still more comfortable with Emacs keys, but I found it easy to add the emacs keys I miss.
Its license is such that even if MS abandons it I suspect the community will keep it going. So give it a try.
Re: Visual Studio Code for Go
#19I've never programmed in Go before. Coming from a C# background. Can someone tell me, how does Go feel? Is is pleasant to work in, or is it tricky like C.
Its a a very simplistic language. Coming from C# there is no inheritance, only composition. Types are super strict too which can be a pain in the ass (especially cuz you cant add things like an int32 and an int64 together). Its nice once you are used to it though.
Re: Visual Studio Code for Go
#20Seems like Acme got a serious competition... :)