You’re absolutely right! Gradle’s toolchain support is a great step forward, and I really like how it can now manage JDKs automatically based on build requireme

You’re absolutely right! Gradle’s toolchain support is a great step forward, and I really like how it can now manage JDKs automatically based on build requirements. That said, the key difference here is when the JDK is provisioned. Gradle’s toolchain support assumes you already have a working Java runtime to start Gradle itself. So on a fresh machine (or CI container) without Java, the build still won’t start. Zero JDK is meant to handle that very first step by making it possible to init in a repo without requiring Java, Maven, or Gradle to be installed at all. It’s basically a lightweight bootstrapper that bridges the gap before the build tools kick in. That said, thanks for sharing. I wasn’t even aware how far Gradle toolchains has come recently. Definitely something I’ll explore further!