After many years away from JVM, I'm back using JVM and Kotlin again with Maven and all the bells and whistles.
I am not happy, compared to my newfound happiness with Makefiles and Go. JVM, Kotlin and Maven seems archaic, granted I've always had that thought, but now it seems like a pain to figure out the pom.xml, modules and waiting for the world to enter my computer by the 1000 and 1000 artifacts Maven will pull in, which half of them I don't believe I need.
My happiness is a Linux machine, with SSH, Vim and VScode with remote extensions and off I program, but not with Kotlin, Java and all the other stuff. I have to figure out the errors, in many various places.
We use AWS CDK, granted it is a nice idea, going from pure CloudFormation files, but a text file has its beauty, all can read the file, no weird syntax, just plain text up and down. It is fast to traverse and fast to deploy using my makefiles. My workflow is beautiful, pure text files.
I really hope some one will pull the plug on all the archaic systems and go back to real textfiles for most of their pipeline.
Integration with CloudFormation is a lot better, as I will be able to call out to AWS CLI and describe my stacks, pull out the values, without importing them and just work. I now if it works on my machine it works in my pipeline, I can rest assured my colleagues will be able to read the file using simple Notepad.
Without downloading half of the worlds repositories to concatenate a string...
Maven, Ant, Jvm is in the past, where the world have moved on the containerization, text files, clarity and simplicity.
Maven, come at me with your stupid dependencies, all your unknown rules and targets and be compared to pure simplicity using
make clean build deploy
mvn dockerfile:build (which doesnt work...) package or was it test before I forgot and don't care