[crabbygrabby]

Go now has generics. The performance of using them is hit or miss it seems.

Your opinion is valid, but I would say, if you aren't juicing for the best performance, you can adopt easier patterns to async. There are comments on this post detailing how to go about doing that. Or yea use another language if you want.

[logicchains]

>you can adopt easier patterns to async

Can I do this without having to wrap half the libraries in the ecosystem if I want to use them without worrying about async? C# has that issue: the ecosystem buys heavily into async, so it can be hard to avoid it.

[crabbygrabby]

Probably depends on what you are using and trying to do. So I'll say 'maybe'.

[gjvnq]

But Go still doesn't have enuns with data like in Rust.