this post was submitted on 06 Feb 2025
19 points (91.3% liked)
Programming
18082 readers
133 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Programming languages come with their own niches, tools, culture, and history. Gradle has lots of verbosity, complexity, and so on. It’s a build system and a dependency manager in one. Other languages separate these duties.
A cultural preference for tools written in specific languages or available for specific platforms exists as well. Lots of C/C++ programmers dislike everything Java. They will cite performance and philosophy. They ask why should they install and manage JVM versions and installs for a task they can do with a make file, a shell script, and Conan/vcpkg.
Not even all Java folks use gradle. maven and ant ant are still around and I’ve seen someone write Java build tasks using rake.
As someone who used gradle then didn't for a few years and looked back it, damn did they absolutely butcher the whole thing, not to mention now with the dual kotlin/groovy stuff the documentation is incomprehensible and achieving something that was easy as fuck in groovy like copying some files is a nightmare in kotlin.
The parallel builds seems to be almost entirely gone, de dependency management got an even weirder file format. I have no idea what they are doing