LiamTheBox@lemmy.world to Greentext@sh.itjust.works · 1 day agoAnon tries programming in Javalemmy.worldimagemessage-square228fedilinkarrow-up1793arrow-down132
arrow-up1761arrow-down1imageAnon tries programming in Javalemmy.worldLiamTheBox@lemmy.world to Greentext@sh.itjust.works · 1 day agomessage-square228fedilink
minus-squareScott@sh.itjust.workslinkfedilinkEnglisharrow-up132arrow-down7·1 day 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-squaretaladar@sh.itjust.workslinkfedilinkarrow-up46arrow-down3·1 day 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-up25arrow-down1·1 day 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·14 hours agoAt that point, just kill the VM the app is running on and deal with the fallout.
minus-squareRogueBanana@lemmy.ziplinkfedilinkEnglisharrow-up6·edit-21 day agoBut none of this is relevant for a hello world program, right?
minus-squareScott@sh.itjust.workslinkfedilinkEnglisharrow-up6arrow-down3·1 day agoYou would be surprised, errors right out of the box on a freshly initialized project aren’t uncommon
minus-squarebabybus@sh.itjust.workslinkfedilinkEnglisharrow-up10·1 day agoAs I’ve been working with Java professionally for years, you’re right, I would be surprised, because that would be really uncommon.
minus-squareMalfeasant@lemm.eelinkfedilinkarrow-up1·16 hours agoDon’t bother learning something new, this guy already knows it.
I’ve worked on a corporate project with multiple Java services, anon isn’t really exaggerating. Java can be a hell scape at times
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.
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
As I’ve been working with Java professionally for years, you’re right, I would be surprised, because that would be really uncommon.
Don’t bother learning something new, this guy already knows it.