I don't think Go's criticism only comes from advanced type folks. People criticize that handling errors is manual, annoying and error prone. People criticize

I don't think Go's criticism only comes from advanced type folks. People criticize that handling errors is manual, annoying and error prone. People criticize that you can't implement your own or new data-structures generically, nobody wants to use a non-generic data-structure, and Go's own data-structures are generic, so people complained that users couldn't do the same. People criticize that the lack of higher level list comprehension or stream-like API for data manipulation is tedious. Implementing a filter as a for loop every time gets repetitive. People criticize that duck typed interfaces can make it hard to track what implements what, and if it makes logical sense or not. Etc. Those are things Java and Python programmers are used too for example, so it's not like the criticism is just from Haskell folks.