4 ms·
They are trying to make gradle better, by implementing a "maven over it" - declarative build configuration. But for time being maven is way easier to configure
by krzyk 3y ago
They are trying to make gradle better, by implementing a "maven over it" - declarative build configuration.
But for time being maven is way easier to configure and understand.
- kaba0 3y agoIt has always been “an imperative code that outputs the declarative configuration that can be used for the build”. Which is a very reasonable thing to do, but unfortunately most people fail to understand that a println in the config file’s global scope is different than inside a closure for a task description.
- troupo 3y ago> but unfortunately most people fail to understand that a println in the config file’s global scope is different than inside a closure for a task description. Literally no one complaining about gradle being slow is doing that. Allmost all of gradle's problems come not from people using it, but from Gradle itself. I mean, you said it yourself: in 15 years the state of their API docs is "okayish". But somehow people are still expected to make sense of this shit because apparently it's a plane? But planes famously have extensive documentation, and procedures, and decades of expertise available. Exactly unlike gradle.
- kaba0 3y agoSo what other general purpose build tool do you recommend/vouch for? I actually really like Mill, but it is very small still. I’m unaware of too many playing in the same categories as Gradle.
- troupo 3y ago"If you say a tool sucks, show me a better one" isn't as good as an argument as you think it is. I know of at least one project who just wrote everything in Python because current build tools invariably suck: https://tonsky.me/blog/python-build/ https://tonsky.me/blog/python-build/