LiamTheBox@lemmy.world to Greentext@sh.itjust.works · 1 month agoAnon tries programming in Javalemmy.worldimagemessage-square49fedilinkarrow-up14arrow-down11
arrow-up13arrow-down1imageAnon tries programming in Javalemmy.worldLiamTheBox@lemmy.world to Greentext@sh.itjust.works · 1 month agomessage-square49fedilink
minus-squareScott@sh.itjust.workslinkfedilinkEnglisharrow-up1arrow-down1·1 month agoI’ve worked on a corporate project with multiple Java services, anon isn’t really exaggerating. Java can be a hell scape at times
minus-squareRogueBanana@lemmy.ziplinkfedilinkEnglisharrow-up1·edit-21 month agoBut none of this is relevant for a hello world program, right?
minus-squareScott@sh.itjust.workslinkfedilinkEnglisharrow-up1·1 month agoYou would be surprised, errors right out of the box on a freshly initialized project aren’t uncommon
minus-squaretaladar@sh.itjust.workslinkfedilinkarrow-up1arrow-down2·1 month agoThey 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.
minus-squareHackerJoe@sh.itjust.workslinkfedilinkarrow-up1·1 month agoBest 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!
minus-squaresuperkret@feddit.orglinkfedilinkarrow-up1·1 month agoAt that point, just kill the VM the app is running on and deal with the fallout.
I’ve worked on a corporate project with multiple Java services, anon isn’t really exaggerating. Java can be a hell scape at times
But none of this is relevant for a hello world program, right?
You would be surprised, errors right out of the box on a freshly initialized project aren’t uncommon
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.
Best with an old and vulnerable log4j on a Windows log server.
At that point, just kill the VM the app is running on and deal with the fallout.