Odd choice. A little more research could've yielded a migration to something like Clojure with the benefits of Lisp and an industry-backed stack (JVM).

Of course using an offbeat stack is going to hurt - doesn't mean you have to give up Lisp too.

A decision made odder still since being an independent project, one would think maximizing individual productivity would be the only hope of yielding anything novel and useful in a field like search that isn't a fitting of an off-the-shelf to a business problem. (Something I've done before, it was quite neat.)

Go is not a language focused around individual productivity in any capacity or scope. It's the language of pyramid-building Egyptian Pharaohs. (Throw 1,000 lives at it, it'll get 'er done...)

I say this as someone rather envious of any language that has a native compiler that builds static binaries. (Oh, OCaml...)

As we ponder on what orangetide is up to, lets keep in mind he's not explained or revealed anything at all about Nuuton and for all we know - could be having us on for the sake of self-promotion/promoting Go.

The incorrect speculation about the origins and purpose of Go make this even stranger.

Go exists to make people like Rob Pike happy. The Plan9 and Suckless community of programmers. Those types. That it happened to solve the problems of some Google programmers who were making it was almost incidental.