LiamTheBox@lemmy.world to Greentext@sh.itjust.works · 6 days agoAnon tries programming in Javalemmy.worldimagemessage-square227fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageAnon tries programming in Javalemmy.worldLiamTheBox@lemmy.world to Greentext@sh.itjust.works · 6 days agomessage-square227fedilink
minus-squareScott@sh.itjust.workslinkfedilinkEnglisharrow-up0·6 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-squareRogueBanana@lemmy.ziplinkfedilinkEnglisharrow-up0·edit-26 days agoBut none of this is relevant for a hello world program, right?
minus-squareScott@sh.itjust.workslinkfedilinkEnglisharrow-up0·6 days agoYou would be surprised, errors right out of the box on a freshly initialized project aren’t uncommon
minus-squarebabybus@sh.itjust.workslinkfedilinkEnglisharrow-up0·5 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-squaretaladar@sh.itjust.workslinkfedilinkarrow-up0·6 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-up0·6 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-up0·5 days 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
As I’ve been working with Java professionally for years, you’re right, I would be surprised, because that would be really 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.