News for hackers. Stuff that matters.

A comment on Kotlin for JavaScript. Parent comment

Re:Kotlin for JavaScript by lenkite on Sunday March 27, 2022 @09:54AM (#30820244)
The only reason Gradle is faster is because it uses a daemon for build caching and leverage JVM code optimization.

Once you apply that same strategy to Maven, it actually tends to beat Gradle in performance too. See Maven Daemon: https://github.com/apache/maven-mvnd

[ Parent | on HN ]
Re:Kotlin for JavaScript by ptx on Sunday March 27, 2022 @10:48AM (#30820640)
And if you build from inside IntelliJ, I think it already does essentially the same thing (unless you tell it not to) by importing the Maven project into its internal build system and using a compiler daemon: https://www.jetbrains.com/help/idea/delegate-build-and-run-a...
[ Parent | on HN ]
Re:Kotlin for JavaScript by InsaneOstrich on Sunday March 27, 2022 @11:46AM (#30821150)
Gradle also has the ability to skip things it has already done. It won't recompile code that hasn't changed, won't run tests that haven't changed, etc
[ Parent | on HN ]
Re:Kotlin for JavaScript by p2detar on Sunday March 27, 2022 @01:19PM (#30821993)
> actually tends to beat Gradle in performance too.

Mvnd seems somewhat recent compared to Gradle’s daemon feature. Are there any measurements that confirm this statement? I don’t find any in the repo?

[ Parent | on HN ]