News for hackers. Stuff that matters.

A comment on Java 12. Parent comment

Re:Java 12 by pjmlp on Wednesday March 20, 2019 @04:04AM (#19439939)
Because Maven doesn't require a background daemon eating 2GB of memory to be fast and IDEs can actually provide code completion and documentation while typing.

Android is the only reason to have to put up with Gradle.

[ Parent | on HN ]
Re:Java 12 by ptx on Wednesday March 20, 2019 @06:57AM (#19440836)
Gradle 5 lets you write the build scripts in Kotlin, which is supposed to address the code completion issue. (And the continuous build mode is a nice feature!)

But, yes, is does use a lot of memory.

[ Parent | on HN ]
Re:Java 12 by pjmlp on Wednesday March 20, 2019 @07:10AM (#19440899)
So I have to use additionally 2GB, adopt yet another programming language, to get back what Maven already gives me out of the box?

Eclipse and Netbeans compile on file save, can't get more continuous than that.

[ Parent | on HN ]
Re:Java 12 by james_s_tayler on Wednesday March 20, 2019 @04:47AM (#19440149)
Fair enough. It doesn't sell me on switching back to Maven. Ram is cheap enough. With 32GB Gradle can have a couple if it wants.
[ Parent | on HN ]
Re:Java 12 by pjmlp on Wednesday March 20, 2019 @06:01AM (#19440533)
Most dev laptops are still running with 8GB.

2GB for a cache that isn't required by alternatives for the same result just feels bad.

And don't get me started into turning build scripts into full blown applications impossible to decipher what is going on without some kind of debugging process.

[ Parent | on HN ]