Live data from Hacker News

Creating the Go Programming Language [audio]

changelog.com

71–80 of 135 posts

Re: Creating the Go Programming Language [audio]

#71
post #66

Slightly off topic: Why was the language named "Go"? I originally assumed that it was an abbreviation of Google (where it was developed) but I can't seem to find an information confirming that...

I recall reading that one of the reasons was the fact that "go" sounded good

1. when used as a keyword to start a "goroutine"

  go f()
2. when used from the command line for compilation etc.

  go build ...
  go get ...

Re: Creating the Go Programming Language [audio]

#72
post #42

Earlier quoted context omitted.

You know it's "free as in freedom, not beer," right?

Go is both free as in freedom _and_ free as in beer. Binaries and source are available for use or modification to anybody, free of charge. No ads either.

Go is free as in freedom and paid for by someone else.

Re: Creating the Go Programming Language [audio]

#74
post #72

Earlier quoted context omitted.

Go is both free as in freedom _and_ free as in beer. Binaries and source are available for use or modification to anybody, free of charge. No ads either.

Go is free as in freedom and paid for by someone else.

Specifically paid for by Google which, as far as I'm concerned, is the definition of ad supported.

Re: Creating the Go Programming Language [audio]

#75
post #63
post #52

Earlier quoted context omitted.

I feel people gave Golang attention because it was a good language. It also has the best standard library I’ve ever seen.

Like a standard library that doesn't even have a max function for integers, or a set type?

It is trivial to write both of these on your own, why do we need unnecessary abstraction for such a simple task.

Re: Creating the Go Programming Language [audio]

#77
post #59

I think I'm the only Go programmer who enjoys the idea behind GOPATH :)

I was annoyed by the change as well, but I kinda like the module system. My biggest complaint is that you can only use different major versions of the same dependencies.

Re: Creating the Go Programming Language [audio]

#78

No progress bar. No fast forward button. No speed-up. Man this UX is frustrating.

With at least Firefox, there's a (non-obvious, due to colouring) progress bar a bit further down. Also lets you drag the play point around, to go back/forward/etc.

Re: Creating the Go Programming Language [audio]

#79

are basic languages good though? the amount of go concurrency bugs I've dealt with has been outstanding and quite brutal over the last few years; I feel like many times the same sort of c "i dont make mistakes" programmers are attracted to go and they also don't make mistakes there as well...

> the amount of go concurrency bugs I've dealt with has been outstanding and quite brutal over the last few years

Concurrency is hard. Maybe something like Erlang does it better, but compared the concurrency options in most popular languages, and the bugs that go along with those options, I think I would far rather deal with them in Go.

Perhaps the only reason you find concurrency issues in Go so frequently is because Go is more often used where concurrency is necessary, due to it being more suitable to writing concurrent code compared to many other popular languages? I certainly find more DOM bugs in Javascript than other languages, but I'm not sure that is a reflection of the language, only where the language is most often used.

Re: Creating the Go Programming Language [audio]

#80
post #73
post #59

I think I'm the only Go programmer who enjoys the idea behind GOPATH :)

\o I still use GOPATH structure since it's such a nice way to organize my code.

I didn’t like it at first but didn’t have much choice. After a while I liked the structure. I don’t even write go anymore and I still use gopath structure for my work
Post reply on HN