• Scott
    link
    fedilink
    English
    arrow-up
    130
    arrow-down
    5
    ·
    19 hours 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
        link
        fedilink
        English
        arrow-up
        7
        arrow-down
        1
        ·
        10 hours ago

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

        • babybus
          link
          fedilink
          English
          arrow-up
          9
          ·
          9 hours ago

          As I’ve been working with Java professionally for years, you’re right, I would be surprised, because that would be really uncommon.

    • taladar
      link
      fedilink
      arrow-up
      46
      arrow-down
      2
      ·
      17 hours 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
        link
        fedilink
        arrow-up
        26
        arrow-down
        1
        ·
        17 hours 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!