Scaling Golang to 192 Cores with Heavy I/O
1–9 of 9 posts
Re: Scaling Golang to 192 Cores with Heavy I/O
#2The name of the language is Go.
Re: Scaling Golang to 192 Cores with Heavy I/O
#3The name of the language is Go.
Ahem.. This seems to have changed but the language was originally released under a website with the domain golang.org
Re: Scaling Golang to 192 Cores with Heavy I/O
#4The name of the language is Go.
> The language is called Go. The "golang" moniker arose because the web site was originally golang.org. (There was no .dev domain then.) Many use the golang name, though, and it is handy as a label. For instance, the Twitter tag for the language is "#golang". The language's name is just plain Go, regardless.
Re: Scaling Golang to 192 Cores with Heavy I/O
#5The name of the language is Go.
Go is a worthless search term, so golang has become the defacto name - and it's better for it.
Re: Scaling Golang to 192 Cores with Heavy I/O
#6The name of the language is Go.
[deleted]
Re: Scaling Golang to 192 Cores with Heavy I/O
#7The name of the language is Go.
You must be fun at parties.
Re: Scaling Golang to 192 Cores with Heavy I/O
#8The name of the language is Go.
It's pronounced "Go" and written "Go" in prose.
It's searched as "Golang" and thus written as "Golang" in places necessary to make search work (titles, keywords, ....)
Not all that different from the various fucked up ways English spelling works
Re: Scaling Golang to 192 Cores with Heavy I/O
#9The name of the language is Go.
When the main debate is over what the language is called, it's a sure sign the actual tech is shit.