Pomni is from The Amazing Digital Circus, a recently released animated pilot where human characters are endlessly tortured by an AI entity in a zany VR world. My best guess is it’s correlating said eternal suffering with using Java/Maven or writing tests? Not sure lol
Also, I assume it’s because the xml file in maven is typically called a “pom” file, so expanding that to pomni for some reason? It still doesn’t make a ton of sense
I had struggled with Gradle off and on for something like five years before eventually learning that Gradle files were executable code files (as opposed to static data files such as .ini) written in Groovy (as opposed to some unique esoteric Gradle lang), and the code within them interacts with implicitly declared objects.
All of that could have been figured out very quickly with a cursory look over the documentation. I just never read it until way past the time I should have. That’s on me. I just wanted the stupid magic Gradle incantation that would get my stupid Minecraft mod to compile.
Also, I gotta say, holy crap I hate Groovy. All of its syntax ““sugar”” just makes it hard to read unless you already know what’s up. The unique ways it makes code look like not code was the bulk of the reason why I took so long to figure out that Gradle files were code in the first place.
I know you can write Gradle files in Java instead of Groovy, but at this point that just seems wrong. Build files shouldn’t look like source files. I have no objective justification for this, it just doesn’t feel like the way.
Pomni is from The Amazing Digital Circus, a recently released animated pilot where human characters are endlessly tortured by an AI entity in a zany VR world. My best guess is it’s correlating said eternal suffering with using Java/Maven or writing tests? Not sure lol
Also, I assume it’s because the xml file in maven is typically called a “pom” file, so expanding that to pomni for some reason? It still doesn’t make a ton of sense
Ding ding ding!
Although Gradle is not much better imo…
You can now write pom.xml in other languages as well if you want: https://github.com/takari/polyglot-maven/
I had struggled with Gradle off and on for something like five years before eventually learning that Gradle files were executable code files (as opposed to static data files such as .ini) written in Groovy (as opposed to some unique esoteric Gradle lang), and the code within them interacts with implicitly declared objects.
All of that could have been figured out very quickly with a cursory look over the documentation. I just never read it until way past the time I should have. That’s on me. I just wanted the stupid magic Gradle incantation that would get my stupid Minecraft mod to compile.
Also, I gotta say, holy crap I hate Groovy. All of its syntax ““sugar”” just makes it hard to read unless you already know what’s up. The unique ways it makes code look like not code was the bulk of the reason why I took so long to figure out that Gradle files were code in the first place.
I know you can write Gradle files in Java instead of Groovy, but at this point that just seems wrong. Build files shouldn’t look like source files. I have no objective justification for this, it just doesn’t feel like the way.