It's bizarre that a one-man-team beats the mighty Google in pretty much everything.
The build is so freaking fast that it runs ProGuard by default – and beats a Gradle build without ProGuard.
That dev implemented and shipped Instant Run way before Google "invented" it, and it's still faster compared to Google's implementation.
Since my focus is the NDK, which keeps being half-done in Gradle, I keep using Ant + ndk-build and have migrated to Visual Studio 2015 for my Android hobby coding.
The plugin can now manage and auto-install SDKs, tools, support repos and NDKs, so no messing around with Google's `android` tool anymore!
Maybe this is of use to you.
https://github.com/scala-android/sbt-android/commit/7b32e55f... https://github.com/scala-android/sbt-android/commit/53b855de...
I thought it was just the plugin and DSL handling code. That would explain why Gradle's so slow, then.
> the DSL, which can be used purely declaratively, but it's not limited to such use
Virtually no-one uses Groovy procedurally, only declaratively, in Gradle build scripts, so although that's true in theory, in practise only the non-Turing Complete portions of Groovy are used. Calling it a programming language there is like calling HTML one because you can embed Javascript in HTML.
For my day job, we use Groovy for our Spring Boot app. I love it.
I've also done a lot of Grails development, which I enjoyed also.
It was even on JEE roadmap to be an alternative language for JSF applications, presented at JSF Days in Vienna.
Nowadays if it wasn't for Gradle, I wouldn't even notice it exists.
Mobile dev being new, even Java developers get to play with more shiny toys. For good or ill...
org.gradle.daemon=true
in your .gradle/gradle.properties.
Slow startup is an old JVM problem.No it not, when people make use of Java code, it starts in ms.
It is only slow when running languages like Groovy or Clojure on top of it.