Step 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. ^_^
Except the Go scheduler is actually pretty complex and really good at what it does...
Creating the Go Programming Language [audio]
31–40 of 135 posts
Re: Creating the Go Programming Language [audio]
#32While I dislike golang its runtime and compiler are nice. Also lot of its simplicity aspects are nice. if vlang can implement what it is trying to implement then probably it will be a nice contender to golang in all aspects. But that looks too good to be true. The other language is rust, but the higher learning curve make it a bit harder for adoption in non systems where go/java like performance is enough.
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.
Re: Creating the Go Programming Language [audio]
#33are 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...
Re: Creating the Go Programming Language [audio]
#34Earlier quoted context omitted.
What qualifies a language as "pretty basic" and why is that a bad or a good thing?
Being basically a copy of Limbo with Oberon-2 method syntax, although we are a bit further than 1992, to start with. And while at it, offering less features as Algol used to have.
Offering less features was literally their goal in which they succeeded
Re: Creating the Go Programming Language [audio]
#35Step 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. ^_^
Except the Go scheduler is actually pretty complex and really good at what it does...
The language is simple, the implementation is anything but.
Re: Creating the Go Programming Language [audio]
#36HN comments seem to lack focus on the podcast's contents (which isn't too surprising, as the podcast is nearly as long as the post is old.) Having already listened, here are some highlights:
* How work started on the language in the beginning, including social factors such as support from their managers.
* The value of starting a language with its spec instead of an implementation. Why it's a good idea and when it's maybe not.
* Learning how to work in on an open source project coming from a closed source world, how to make that project successful.
* Feature rich vs feature parse languages. What Go chose, and the trade-offs it took when choosing so.
* What influences Go has had on other programming languages, with a focus on gofmt and code formatting in general.
Re: Creating the Go Programming Language [audio]
#37Re: Creating the Go Programming Language [audio]
#38Step 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. ^_^
What qualifies a language as "pretty basic" and why is that a bad or a good thing?
It offers developers less opportunity to show off how smart they are vs shipping stuff that works.
Go is outstanding for the latter.
Re: Creating the Go Programming Language [audio]
#39Step 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.
Yes. Together with Jetbrain's Goland IDE, Go's simplicity allows for most engineers to hit the ground running in Go projects despite not having familiarity with the language. At least that was my experience while working in a team with newcomers.
The lingering issue was package management but then came Go modules and slowly but surely the community is migrating to it from godep and other tools.