LiamTheBox@lemmy.world to Greentext@sh.itjust.works · 8 days agoAnon tries programming in Javalemmy.worldimagemessage-square248fedilinkarrow-up1870arrow-down135
arrow-up1835arrow-down1imageAnon tries programming in Javalemmy.worldLiamTheBox@lemmy.world to Greentext@sh.itjust.works · 8 days agomessage-square248fedilink
minus-squareScott@sh.itjust.workslinkfedilinkEnglisharrow-up143arrow-down7·8 days 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-up51arrow-down3·8 days 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-up29arrow-down1·8 days 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-up3·7 days agoAt that point, just kill the VM the app is running on and deal with the fallout.
minus-squareRogueBanana@lemmy.ziplinkfedilinkEnglisharrow-up7·edit-28 days agoBut none of this is relevant for a hello world program, right?
minus-squareScott@sh.itjust.workslinkfedilinkEnglisharrow-up8arrow-down3·8 days agoYou would be surprised, errors right out of the box on a freshly initialized project aren’t uncommon
minus-squarebabybus@sh.itjust.workslinkfedilinkEnglisharrow-up14·8 days 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·7 days 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.