5 ms·

Go almost instant build time is a huge productivity boost when compared to Java. You get both the solidity of a typed language, and the development speed of int

Go almost instant build time is a huge productivity boost when compared to Java. You get both the solidity of a typed language, and the development speed of interpreted languages (py, js).

troupo 3y ago
Java's build times are very fast. Java's build tools are anything but. And I'm surprised no one is doing anything about it.
- palata 3y ago
  That's because everybody is busy shipping full web browsers with a hard-coded website inside and calling that an "app".
- lenkite 3y ago
  If you are leveraging Maven, use mvnd during development: https://github.com/apache/maven-mvnd https://github.com/apache/maven-mvnd
- kaba0 3y ago
  Gradle, when the daemon is runnning is very fast, people just often fck up their build scripts to include config-time run functionality, which is just all around a stupid thing to do. It only ever runs tasks that actually have to be run, has integration with javac, can work in parallel, and even has cross-company build caches if needed. Also don't forget that Java can do hot reloads with the debugger, or with tools like JRebel. Certain frameworks support it 100% and it will be much much faster than whatever go does.
  - troupo 3y ago
    I've never seen Gradle run fast, even with the daemon running. Gradle itself can take multiple seconds to startup. God knows what it's doing.
    - MrBuddyCasino 3y ago
      Gradle is steaming pile of garbage. But since the zoomers are allergic to XML, Maven (actually fast) is slowly dying.
      - kaba0 3y ago
        Gradle is much faster than maven as it can properly parallelize the workloads. Sure, it won’t be visible on a hello world, though.
        MrBuddyCasino 3y ago
        Has never been the case in my many years of using it. Hundreds of MB permanent RAM usage for the daemon (which it wouldn’t require if it was properly designed), everything taking well above 10s. None of this has ever been an issue with Maven.
        kaba0 3y ago
        You can disable the daemon in gradle if you don’t want it.
        troupo 3y ago
        I've never seen gradle be faster than Maven. I have no idea what purose its daemon serves or its promise to "parallelize workloads". Which workloads? Its purpose is to build the project, fast. It spends about a magnitude of time more just trying to start up, even with daemon running.
        throwaway2037 3y ago
        There seems to be some disagreement to your statement. Can you provide some concrete examples?
        kaba0 3y ago
        https://gradlehero.com/maven-vs-gradle-comparison/ https://gradlehero.com/maven-vs-gradle-comparison/
  - SpaghettiCthulu 3y ago
    Gradle is anything but fast
- throwaway2037 3y ago
  If you avoid pre-Java 11 modules in Apache Maven, it is very fast to build. Plus, IntelliJ is auto-magically incremental build. Can you give some specific examples where Java build tools are slow? Most Java developers spend their whole day in an IDE that is doing incremental build, jumping in and out of a debugger to fix bugs or broken unit tests.
  - troupo 3y ago
    Maven is okay-ish, Gradle is an abomination. Incremental compilation doesn't always work, and the fact that the build tools often spends a magnitude or more time just starting up than actually doing useful work is inexcusable.

Go almost instant build time is a huge productivity boost when compared to Java. You get both the solidity of a typed language, and the development speed of interpreted languages (py, js).

troupo 3y ago

Java's build times are very fast. Java's build tools are anything but. And I'm surprised no one is doing anything about it.

palata 3y ago
That's because everybody is busy shipping full web browsers with a hard-coded website inside and calling that an "app".
lenkite 3y ago
If you are leveraging Maven, use mvnd during development: https://github.com/apache/maven-mvnd https://github.com/apache/maven-mvnd
kaba0 3y ago
Gradle, when the daemon is runnning is very fast, people just often fck up their build scripts to include config-time run functionality, which is just all around a stupid thing to do. It only ever runs tasks that actually have to be run, has integration with javac, can work in parallel, and even has cross-company build caches if needed. Also don't forget that Java can do hot reloads with the debugger, or with tools like JRebel. Certain frameworks support it 100% and it will be much much faster than whatever go does.
- troupo 3y ago
  I've never seen Gradle run fast, even with the daemon running. Gradle itself can take multiple seconds to startup. God knows what it's doing.
  - MrBuddyCasino 3y ago
    Gradle is steaming pile of garbage. But since the zoomers are allergic to XML, Maven (actually fast) is slowly dying.
    - kaba0 3y ago
      Gradle is much faster than maven as it can properly parallelize the workloads. Sure, it won’t be visible on a hello world, though.
      - MrBuddyCasino 3y ago
        Has never been the case in my many years of using it. Hundreds of MB permanent RAM usage for the daemon (which it wouldn’t require if it was properly designed), everything taking well above 10s. None of this has ever been an issue with Maven.
        kaba0 3y ago
        You can disable the daemon in gradle if you don’t want it.
      - troupo 3y ago
        I've never seen gradle be faster than Maven. I have no idea what purose its daemon serves or its promise to "parallelize workloads". Which workloads? Its purpose is to build the project, fast. It spends about a magnitude of time more just trying to start up, even with daemon running.
      - throwaway2037 3y ago
        There seems to be some disagreement to your statement. Can you provide some concrete examples?
        kaba0 3y ago
        https://gradlehero.com/maven-vs-gradle-comparison/ https://gradlehero.com/maven-vs-gradle-comparison/
- SpaghettiCthulu 3y ago
  Gradle is anything but fast
throwaway2037 3y ago
If you avoid pre-Java 11 modules in Apache Maven, it is very fast to build. Plus, IntelliJ is auto-magically incremental build. Can you give some specific examples where Java build tools are slow? Most Java developers spend their whole day in an IDE that is doing incremental build, jumping in and out of a debugger to fix bugs or broken unit tests.
- troupo 3y ago
  Maven is okay-ish, Gradle is an abomination. Incremental compilation doesn't always work, and the fact that the build tools often spends a magnitude or more time just starting up than actually doing useful work is inexcusable.