I hate listicles, and I am highly hoping that this doesn’t become one of them. Yet, I somehow felt the need to write down the reasons why I am giving Go a second (or maybe, third 🤔) chance. To the Java developers out there, searching for a new weapon of choice, I am hoping that this will give you a bit of perspective. This is not a description of Go-specific features.

Often, the seemingly simple things can make you spend hours chasing around your tail. Like trying to connect to a MongoDB instance using KMongo. Basically, if you have checked out the KMongo quick start, setting up a client and fetching some data should be extremely easy: val client = KMongo.createClient() //get com.mongodb.MongoClient new instance val database = client.getDatabase("test") //normal java driver usage val col = database.getCollection<Jedi>() //KMongo extension method The quick start tutorial assumes that your DB resides on mongodb://localhost:27017, but in reality, your MongoDB connection string looks more like this:

NOTE: This post was originally intended to provoke a discussion, and despite its length, the original goal is still the same. Please, share your feedback on Twitter, Reddit, or Dev.to. My experience with the JVM dates back from around 2010. Java in those days was a bit different from todays’ standpoint. Java 6 was the current standard at the time, but most projects I got to work on, were stuck between Java 4 and 5.