4 ms·
The go team had the entire power of Google to subtly rebuild their search engine to not suck for this one stupid naming choice. I remember the earliest days aft
by techdragon 5y ago
The go team had the entire power of Google to subtly rebuild their search engine to not suck for this one stupid naming choice. I remember the earliest days after the language’s name was announced… it was nearly impossible to search for anything to do with it. It took months for anything to get better. The early conventions of calling it “go-lang” or “golang” stem from these days when it was just utterly impossible… and then Google realising they were affecting their recruitment pipeline (which Go was explicitly designed to help) stepped in to help fix the search discoverability so it wasn’t impossible to learn about this new language that people outside of Google should learn so Google didn’t have to teach its recruits the language designed for them.
In case the tone comes across harsh, I was trying to hold back just how I really feel. I can read and write in Go, but I hate the entire language and it’s ecosystem. It’s obvious to me that it was designed to be a better Java for Googlers at Google living in a monorepo world… the only positives I have to say about it are that talented people have somehow managed to write excellent and useful tools and software using it, but I really can’t like a language that makes me feel like I’m programming with the accidental child of BASIC and Java. However this isn’t a thread about Go, I just wish the poor choice of name had doomed it to obscurity and a quick death.