Earlier quoted context omitted.
From everything I've read, by people versed in compilers, the implementation is pretty basic too (regarding optimizations, shortcuts, compiler design, etc). In fact, the Go core team themselves have said time and again that they preferred simple implementations and implementation convenience over more powerful but complex ones...
The Go implementation has gotten more sophisticated over time. It now has an optimizing SSA backend, a rather intricate GC, etc. I still disagree with a fair number of the Go implementation design decisions, but I certainly wouldn't call the compiler a basic implementation anymore.
Creating the Go Programming Language [audio]
61–70 of 135 posts
Re: Creating the Go Programming Language [audio]
#62Earlier quoted context omitted.
From everything I've read, by people versed in compilers, the implementation is pretty basic too (regarding optimizations, shortcuts, compiler design, etc). In fact, the Go core team themselves have said time and again that they preferred simple implementations and implementation convenience over more powerful but complex ones...
The Go implementation has gotten more sophisticated over time. It now has an optimizing SSA backend, a rather intricate GC, etc. I still disagree with a fair number of the Go implementation design decisions, but I certainly wouldn't call the compiler a basic implementation anymore.
Re: Creating the Go Programming Language [audio]
#63Earlier quoted context omitted.
Pretty much this, the only reason anyone gave Go any attention was: 1. The pedigree of the creators 2. Google's developer marketing And now we are stuck with it thanks to traction.
I feel people gave Golang attention because it was a good language. It also has the best standard library I’ve ever seen.
Re: Creating the Go Programming Language [audio]
#64Earlier quoted context omitted.
I mean, Crystal would be my next go-to. If you have never written Ruby (like me) the appeal isn't the Ruby-like syntax, it's just a reasonable syntax with a very pragmatic type system and niceties (like classes, which are more open to hacking / composition than in other languages). It's like Go++ in my mind.
Crystal is dead, exactly how can you expect to have a language that compete with Go with only 2 full time devs?
Re: Creating the Go Programming Language [audio]
#65are 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...
After I did a million lines in C (way back when), I still made mistakes (but fewer! still: not none!), but I had built better tooling and processes to help me find them earlier.
I was (as you say) attracted to Go, but with less accumulated tooling, the bugs take longer to find (that, and playing around with CSP, I guess, which is my own damn fault).
Re: Creating the Go Programming Language [audio]
#66I originally assumed that it was an abbreviation of Google (where it was developed) but I can't seem to find an information confirming that...
Re: Creating the Go Programming Language [audio]
#67There is no transcript.
Re: Creating the Go Programming Language [audio]
#68Re: Creating the Go Programming Language [audio]
#69Step 1: be rob pike. Step 2: invent a pretty basic programming language using your old compiler from Plan 9 while at google. Step 3: be rob pike. ^_^
The basic-ness of golang is the best part about it.
Re: Creating the Go Programming Language [audio]
#70Slightly 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...