Nice thing about Go is that it is really simple and it does not force principles of OOP by default. If you have learned C, Go (or Rust if you want something more difficult to comprehend) should be your next step.
I started learning Go and still like it. Though I've been swoon to the likes of kotlin. It has native bindings if you want. Swap go functions for coroutines. Channels are in experimental. You also have closures and immutables. So if you're heavy Java why Go vs Kotlin?
My biggest gripe and complement are the same it was designed with ease in mind but that leads to a lot of imparative code and a lot of boiler plate and 2.0 generics and different error handling a lot want and others dont. I do like Go but I've seen kotlin and Id rather do that to each there own.
Hi David, I appreciate your comment, I haven't use Kotlin at all by the time. I saw Go at first and feel very comfortable with what they bring and experiment how I can get good results, if the code is well done. I would have to test a Kotlin to be able to compare it with Go(And now I will add it to my research list). But anyway, I think, is not about the language anymore, is more about how and why we choose it. Maybe Kotlin could be better for some specific things based on the languages features, but this desition has to be made thinking in the purpose of the software.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.