News for hackers. Stuff that matters.
Re:I/O is no longer the bottleneck by taf2 on Saturday November 26, 2022 @09:37AM (#33752988)
I never remember it being sold as a C killer maybe as a Java killer?
Re:I/O is no longer the bottleneck by habibur on Saturday November 26, 2022 @09:49AM (#33753077)
It was sold as C killer in the beginning.

And then a few years later there was an article that said, the Go engineers were surprised when they saw C/C++ coders weren't switching to Go rather Python/Ruby coders were "upgrading" to Go.

Re:I/O is no longer the bottleneck by capableweb on Saturday November 26, 2022 @10:02AM (#33753188)
golang.org circa 2010:

> go is ... fast

> Go compilers produce fast code fast. Typical builds take a fraction of a second yet the resulting programs run nearly as quickly as comparable C or C++ code.

https://web.archive.org/web/20100217123645/http://golang.org...

That seems to me like they were trying to say "If you want C/C++ performance but nicer/easier syntax, you can use Go", which turned out to be not that true in the end.

Edit: the old "Language Design FAQ" also goes further in detail on how the envision (the first version of the) language: https://web.archive.org/web/20100211104313/http://golang.org...

Re:I/O is no longer the bottleneck by dagw on Saturday November 26, 2022 @10:22AM (#33753350)
It was more sold as a C++ killer than a C killer.
Re:I/O is no longer the bottleneck by forty on Saturday November 26, 2022 @10:46AM (#33753530)
I believe Go was created to replace python at Google.