@LiamTheBox to [email protected] • 1 day agoAnon tries programming in Javaimagemessage-square225arrow-up1792arrow-down132
arrow-up1760arrow-down1imageAnon tries programming in Java@LiamTheBox to [email protected] • 1 day agomessage-square225
minus-squareScottlinkfedilinkEnglish130•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-square@[email protected]linkfedilink47•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-square@[email protected]linkfedilink26•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-square@[email protected]linkfedilink1•9 hours agoAt that point, just kill the VM the app is running on and deal with the fallout.
minus-square@[email protected]linkfedilinkEnglish6•edit-223 hours agoBut none of this is relevant for a hello world program, right?
minus-squareScottlinkfedilinkEnglish4•22 hours agoYou would be surprised, errors right out of the box on a freshly initialized project aren’t uncommon
minus-squarebabybuslinkfedilinkEnglish12•21 hours agoAs I’ve been working with Java professionally for years, you’re right, I would be surprised, because that would be really uncommon.
minus-square@[email protected]linkfedilink1•12 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.