Gradle: Code-Based Builds, Not XML

WHY IT EXISTS: Build tools like Apache Maven used rigid, declarative XML files to define a project's structure and dependencies. For complex projects, this led to verbose and inflexible configurations. Gradle was created to provide a more powerful, code-based approach to build automation, offering the flexibility of a real programming language.

THE MENTAL MODEL: Gradle treats your build definition as a program, not just static configuration. Instead of declaring project settings in XML, you write scripts using a Domain-Specific Language (DSL) in Groovy or Kotlin. This allows you to use variables, control flow, and custom logic to define how your software is compiled, tested, and packaged.

HOW IT WORKS: At its core, Gradle models your build as a Directed Acyclic Graph (DAG) of tasks. Each task represents a unit of work, like 'compileJava' or 'runTests'. When you initiate a build, Gradle analyzes these task dependencies to create an execution plan, ensuring everything runs in the correct order. The entire process is executed on the Java Virtual Machine (JVM).

WHEN TO USE IT: Use Gradle for multi-language projects or projects with complex build requirements that don't fit a conventional structure. It excels at managing tasks like compilation, testing, and publishing for applications using Java, C/C++, or JavaScript, especially when you need programmatic control over the build process.

WHEN NOT TO USE IT: For very simple projects with a standard lifecycle that fits perfectly within a conventional model (like a basic Maven project), Gradle's power can be overkill. The added complexity of a programmable build script can introduce maintenance overhead that a simpler, declarative tool avoids.

ONE CANONICAL EXAMPLE: Migrating a multi-module Java project from Maven. In Maven, sharing configuration between modules requires complex XML inheritance. In Gradle, you can write a script in the root project's build.gradle file that programmatically configures all sub-projects, applying plugins and defining shared dependencies with a few lines of code.