News for hackers. Stuff that matters.
Re:Pkg.go.dev is more concerned with Google's interests than... by ocdtrekkie on Saturday August 01, 2020 @07:02PM (#24024669)
FWIW, Drew's position on Go is hardly even unique. Someone who is quite fond of Go was telling me last week about how I should consider learning it despite it being from Google, because it is not very Google-like of a project. And that wasn't the first time I'd heard it either.

(Myself, I am usually just trying to build stuff people wrote in Go, and I usually end up fighting the tooling for a while and getting mystified by the error messages and having no idea where to look to solve them.)

Re:Pkg.go.dev is more concerned with Google's interests than... by arp242 on Saturday August 01, 2020 @07:18PM (#24024774)
I avoided Go for years because it was from Google until I quite accidentally landed a Go job several years ago, and I haven't looked back. Amusingly, I am now using Go to build a competitor for Google Analytics. Heh.

It was an important lesson in a way, as it taught me that Google – or indeed, any organisation comprised of thousands of people – is not a single monolithic entity.

Also, feel free to drop me a line if you've got problems with a specific error, and I can perhaps point you in the right direction.

Re:Pkg.go.dev is more concerned with Google's interests than... by ocdtrekkie on Saturday August 01, 2020 @07:41PM (#24024918)
I did get the thing last week to build! :) My Go-recommending friend seemed to think the script I was using was pulling in Go 1.11 where modules were not as well supported as they are now? But I got around it.

It was just that the error message I got really gave me nothing useful to search for. Literally was a "permission denied" error... while "go build"ing stuff with effective superuser. It wasn't really pointing me at what it didn't have permission to do or how I would go about getting it.

Re:Pkg.go.dev is more concerned with Google's interests than... by arp242 on Saturday August 01, 2020 @07:58PM (#24025032)
"Permission denied" usually happens when it tries to build stuff in "GOROOT", that is, the standard library installed in /usr/lib/go or some such. This normally shouldn't happen, so there's probably something wrong with your installation or setup. Hard to be 100% sure though, that's just the usual cause in my experience.

I think Debian ships with Go 1.11 in current stable (and by extension, Ubuntu too, I assume?). The entire GOPATH to modules switch is messy, ugly, broke a lot of stuff, and is confusing for newcomers, even though modules is clearly better. I think we're finally nearing the end of it though.

You probably want to just use Go 1.14 (the latest version) if you can. The language itself is very stable (just not the surrounding tooling).

Re:Pkg.go.dev is more concerned with Google's interests than... by ocdtrekkie on Saturday August 01, 2020 @08:01PM (#24025050)
I can definitely say it's the tooling that throws me every time. And I do think we pull from Debian for that script currently, though we're going to update it soon. (I think I was told 1.15 was near anyways?)
Re:Pkg.go.dev is more concerned with Google's interests than... by arp242 on Sunday August 02, 2020 @12:29PM (#24029635)
Overall I find that the tooling is actually really nice, and better than anything I've worked with previously. It's just this weird "old method vs. new method" schism that makes it hard :-/ It's restricted to just tooling, but kind of Go's Python 3 moment.

And yeah, I believe Go 1.15 should be released in August. rc1 was released last week or so.