Hacker News Reader

Comment by cube2222 | Hacker News Reader

For anybody wondering if vgo is production ready, we've been using it since it came out in go 1.11 and so far didn't have any problems.

Existing workflows don't break because there's the vendor command and dependency management is instantaneous. You can also roll it out gradually as it doesn't have any problems depending on non-module repositories (using commit hashes and dates)

There's a great blog post series too if you're interested in the internals of go modules: https://research.swtch.com/vgo (it's also one of the good counterexamples to people claiming go ignored x years of PL research and history)

View on HN

I found the editor support to be still somewhat hit and miss though. VsCode go extension still does not work as good on module enabled projects for example. Otherwise we did not face any issues either.

Oh yeah, that's something I heard about from my coworkers. Goland had support for go modules since the 1.11 prerelease as far as I remember, so I hadn't experienced it myself.

However, most tooling works if you use go mod vendor prior to using it, that was the case for me at least when using linters and similar stuff.

I also got this problem when using modules with go mod but then I did "go mod vendor" and all extensions are now happy again for that project! :)

That's a great reason to try out Goland, which has had excellent module support since day 1.

If you can afford that $100-200/year subscription.

Which most professionals are able to.

I mean, if you're a professional Go developer, then yes, you can? You could even expense it or write it off.

> You could even expense it or write it off.

If you only use it for your employer's code, sure. Otherwise it's a license violation. Personally, I think it's better to buy an individual license, which you can use for your day job as well as long as you are not compensated for it.

But that’s the point isn’t it? Goland clearly goes above and beyond what free and open source can provide, so don’t feel like you’re getting ripped off paying for an IDE.

I bought it and stopped using it. It does work with modules, but I don't like the IDE itself and went back to vs code even though it breaks on me regularly. The UI/UX is just too foreign for me in GoLand. I had to search Google to find out how to search the project. Everything I wanted to do was non-discoverable for me.

CMD+SHIFT+F just like any other editor (vscode, sublime etc) out there?

Also you have action manu on CMD+SHIFT+A that will give you any command IDE can offer.

It's as discoverable as vscode if not more (you can even use IDE Features Trainer plugin if you want to)

Pretty sure cmd+shift+f (maybe it was just cmd+f) would search the open file.

With Shift: search whole Project. Without: search in open editor

It's much better to get IntelliJ Ultimate, in case you code in other languages, which I assume, most do. And it comes with a full-featured DataGrip.

Well, GoLand is $89/yr for the first year, with their standard continuity discounts for further years. $200/yr is only for orgs - if you're paying for it yourself, that's not the price you should be getting.

(I've been using GoLand since when they were calling it Gogland - no complaints so far)

every 6 months I spend half a day trying to get gocode and whatnot to work with my IDE and still can't get a reliable fix. Go modules really messed up a lot of dev tooling

I had the same problem with Emacs, couldn't get it to work reliably.

with the addition of the `gopls` tool (https://github.com/golang/go/wiki/gopls), this shouldn't be nearly as much of a problem in the coming years.

> For anybody wondering if vgo is production ready, we've been using it since it came out in go 1.11 and so far didn't have any problems.

As a 2nd datapoint: We've been using it since 1.11.2, and have had problems, but have had no problems since 1.12.

Should anyone be using vgo anymore? The regular go command supports modules now.

Indeed, I meant go modules saying vgo.

Reply on news.ycombinator.com