LiamTheBox@lemmy.world to Greentext · 19 hours agoAnon tries programming in Javalemmy.worldimagemessage-square159fedilinkarrow-up1669arrow-down127
arrow-up1642arrow-down1imageAnon tries programming in Javalemmy.worldLiamTheBox@lemmy.world to Greentext · 19 hours agomessage-square159fedilink
minus-squareScottlinkfedilinkEnglisharrow-up130arrow-down5·19 hours 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-up5·edit-211 hours agoBut none of this is relevant for a hello world program, right?
minus-squareScottlinkfedilinkEnglisharrow-up7arrow-down1·10 hours agoYou would be surprised, errors right out of the box on a freshly initialized project aren’t uncommon
minus-squarebabybuslinkfedilinkEnglisharrow-up9·9 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-squaretaladarlinkfedilinkarrow-up46arrow-down2·17 hours 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-up26arrow-down1·17 hours 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!
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.