haha, yeah, lisp is a cool language. I use a lot of functional constructions in my work. But I couldn't live without channels, goroutines and interfaces. Like, I looked at Rust's coroutine implementations. So clunky and unintuitive and difficult to use.

And interfaces are also very rare to find anywhere, the main other one is Java. But I've always thought that this kind of "fat pointer" dynamic type was the most efficient and semantically clean way of doing dynamic typing.

My quibbles with go are mostly quite superficial and unimportant. Like, I disagree with several rules in gofmt, especially one liners for for and if blocks.

But I also very strenuously disagree with the use of variants as return values. It poisons all the RPC APIs with these assumed constructs that omit handling partial error conditions that are not failures, like getting a result, but not being able to query for the latest version, this is a result, with a proviso, an error condition that is not critical. Variants as return values assumes that all error states are critical, which is ridiculous, ever heard of "warnings" lol. I mean, imagine a shell that doesn't print a prompt??

Also, generics, I simply don't see the point of them. I also don't really understand why more easy tools for building generators aren't out there. Well, maybe I just never looked because they were not around before. Scaffolding tools could do this kind of task quite well. I've written simple AST walking code to implement a code block sorter once, that properly associates doc comments in the tree and I think I even got it to retain relative position of unconnected comment blocks to appear above where they were originally found, though often these kinds of comments are grouping a list of things.