Thread with 8 posts
jump to expanded postif you force me to commit a 53KB jar file and multiple shell scripts into my project's VCS because that is simply The One True Way to use your build systemβ¦
may your descendants be cursed by large .git directories for 10,000 generations
also may the complete absence of license headers on these files haunt you to your grave
dear whoever decided this is The Only Correct Way to use gradle, which is sadly the only practical way to build my project on Android:
i am going to hold a grudge against you until you convince the gradle project to sanction a more reasonable way of doing this, ok? ok.
(it is taking me So much restraint to not just use the f word)
also isn't it absurd that you need a one-hundred-and-sixty-line shell script just to run a jar file, which is supposed to be portable
@hikari I have yet to have a proper positive experience with Java after the first few years it was out. It has just turned into the most obfuscate mess of over design and the least easy to deal with solutions possible.
If I see that anything is related to Java I want to avoid it.
YMMV.
@breadbin I've occasionally had pleasant interactions with it but I do find Java frameworks tend to be overwrought
@hikari I think I have an unusual low threshold for putzing around to get things running something basic. My goal is that it should be easy, and never include scripts, make, etc.
I like go :)