Hand-cranker here. What we seek is bliss, nirvana, not trying to shove square pegs into round holes. We like F#, Haskell and Rust more.

On a more serious note, Go pisses me off every other day. Just off the top of my head, it's pedantic where it shouldn't and vice versa. I get that commented out usages of a variable are not OK for production, but why don't you give me an escape hatch, like --dev flag? And it won't complain about dead code at all if you stick an unconditional return in a middle of a function! Ugh.

Ask, and ye shall receive: https://github.com/kstenerud/go#the-go-programming-language

I mean, strictly speaking I should downvote you for tone... but I am laughing ;-)

I know people who work at Capital One, I wonder how extensive Go usage is there...

I have started looking at job postings recently and I see a lot that have aspirational-Go in their postings. I have managed to avoid Go during my tenure here at Google (which isn't hard since it's not used much at all, despite what people outside of Google seem to think), but I'm starting to worry that if I move on I'm going to have to take a job writing it.

Who is hiring remote for Rust, Zig, OCaml, or Erlang? Those seem more palatable to me? :-)

Before learning a new language I always look at Linkedin for open jobs. Last week, I could find next to nothing for anything Rust and OCaml. I eventually decided to modernize my C++ skills to be relevant again

What does aspirational-Go means?

I assumed it was job posts in the vein of "new code written in Go" or "migrating systems to Go", kinda like when somebody says "monolith moving to microservices" but actually you spend 95% of the time working on the monolith.

Tell me there isn't a crowd latched on to "safety" that adds nothing else to every Go discussion.