tmpxkdks

He knows that rust posts are usually popular here. It is just clickbait.

AFAIK, Go doesn't use libc.

Anyway, it is still a problem if you encounter a bug in any dependencie: you have to recompile every application using it.

> abstraction/polymorphism, concurrency and dependency management which are all simpler and clearer in Go than in Java

Really? A lot of copy/pasted code, generics replaced with casts on empty interfaces, poor support for collections, only very primitive concurrency tools, and so on...

I can understand that simplicity is good for small CLI/network tools, but it is hardly an alternative for really big applications where Java is vastly used