• Scott@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 month ago

    I’ve worked on a corporate project with multiple Java services, anon isn’t really exaggerating. Java can be a hell scape at times

      • Scott@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        You would be surprised, errors right out of the box on a freshly initialized project aren’t uncommon

    • taladar@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      arrow-down
      2
      ·
      1 month ago

      They forgot to mention that production Java applications apparently need to log a certain minimum number of completely meaningless stacktraces per hour to work properly. Or at least I assume that is the case from the fact that all of them do that.

      • HackerJoe@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        Best with an old and vulnerable log4j on a Windows log server.

        We don’t know what’ll happen if we update. And we don’t know if the dude who coded it will answer our calls. YOLO!