3 ms·

Except Gradle is worst ...

• aphexairlines 7y ago
  Feel free to use Bazel or Pants or Mill or Maven or Fury if Gradle isn't your cup of tea.
• swish_bob 7y ago
  Gradle is so much better than maven it's not even funny. Every time I check out a project in maven these days, I flinch.
  • pjmlp 7y ago
    Every time I get to do a Gradle build I have enough time to go out for lunch.
    • danielscrubs 7y ago
      If true, I’m curious as to why. They call the same compiler and both support incremental compilation.
      • pjmlp 7y ago
        Because Gradle requires an additional daemon sucking up 2GB and uses Groovy for plenty of its tasks, instead of using declarative builds implemented in Java without using background daemons. I seldom see conference talks how to optimize Maven builds, Gradle talks about build optimization, at least one per Java conference, and several per Android one. Just Google IO 2019 had three talks about it.
        • swish_bob 7y ago
          That's just bizarre. And so far removed from my experience I'm genuinely surprised. I've never had a gradle build that didn't manage to remember I've only just compiled the code and haven't changed any of it. I can't remember ever having a maven build that could tell I didn't need to compile every single time. And the same the whole of the way down the stack. Nice attempt to imply gradle isn't declarative though.
          • pjmlp 7y ago
            Fortunately there are plenty of blog posts from Gradle blog and conference talks that prove otherwise. Again just Google IO 2019 has three talks about tackling build performance issues. Maven never required a build performance profiler tool. Gradle is just like Ant, give DevOps a programming language DSL and they will make a mess of build scripts.