• taladar@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    21 hours ago

    Pretty much any compiled language using native binaries is easier to install and distribute. Java applications are an absolute pain to get to run to the point that most need specialized wrapper scripts (usually in shell on unix platforms) and need to tinker with memory management parameters on almost all of them.

    • Schtefanz
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      20 hours ago

      Do you mean something like c or c++ where you have to deal with big little edian, libc, utf8, platform specific threads, various compilers feature sets and a lot of undefined behaviour. Also if you want to distribute a library it is much harder because you a have to package it yourself or what for a distro to package your library or build a header only library which has to be manually updated every time a new version comes out. With maven you just have to upload it and you can use it in another project

      How often do thinker with the memory management in Java? Just use the g1 garbage collector, which will be fine most of the time if you have a problem just use another one.

      You can also compile the program with GraalVM to a native binary, also most Java programs are servers where it make sense to have a systemd service to configure the server

      • taladar@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        19 hours ago

        How often do thinker with the memory management in Java?

        As a sysadmin unfortunately every single one of those shitty Java projects forces me into dealing with that sooner or later.