I've been in a go job recently, and I have to say, I hate the entire language - a lot - except goroutines. I normally complain a lot (in my head to myself, not to anybody else) about literally everything not being written in Java, but with for this service go was actually a really solid choice at the time. The green thread approach + writing "blocking" code is far superior to async/await or event-based code and the product wouldn't been a mess if it were using a less straightforward programming model.
But now that Java has the same feature in the form of virtual threads, I'm once again back to complaining!
Comments
I've been in a go job recently, and I have to say, I hate the entire language - a lot - except goroutines. I normally complain a lot (in my head to myself, not to anybody else) about literally everything not being written in Java, but with for this service go was actually a really solid choice at the time. The green thread approach + writing "blocking" code is far superior to async/await or event-based code and the product wouldn't been a mess if it were using a less straightforward programming model.
But now that Java has the same feature in the form of virtual threads, I'm once again back to complaining!
Ok. But, surely there are places you could go and use Java.
Language choice is low on my list of reasons I choose a company, but there's no law that says I can't still complain to myself ;)