LiamTheBox@lemmy.world to Greentext · 2 months agoAnon tries programming in Javalemmy.worldimagemessage-square248fedilinkarrow-up1882arrow-down136
arrow-up1846arrow-down1imageAnon tries programming in Javalemmy.worldLiamTheBox@lemmy.world to Greentext · 2 months agomessage-square248fedilink
minus-squareScottlinkfedilinkEnglisharrow-up146arrow-down9·2 months 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-squaretaladarlinkfedilinkarrow-up53arrow-down6·2 months 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-squareHackerJoelinkfedilinkarrow-up30arrow-down1·2 months 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-up4·2 months agoAt that point, just kill the VM the app is running on and deal with the fallout.
minus-squareRogueBanana@lemmy.ziplinkfedilinkEnglisharrow-up8·edit-22 months agoBut none of this is relevant for a hello world program, right?
minus-squareScottlinkfedilinkEnglisharrow-up9arrow-down3·2 months agoYou would be surprised, errors right out of the box on a freshly initialized project aren’t uncommon
minus-squarebabybuslinkfedilinkEnglisharrow-up15·2 months 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·2 months 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.