I’m pretty sure Java doesn’t have pointers, so writing a hello world application isn’t gonna fuck up nearly that hard.
The one thing he forgot though is that your source file is probably in
com/companyname/net/classes/factory/factoryfactory/worker/lib/bin/refresh/jdk/model/ui/closebutton/press.java
And spread out among a million other directories, and the java file is like…3 lines. But there are 10k files spread all around directories like this that are all 3 lines a piece with a class definition.
scottmeme@sh.itjust.works 5 weeks ago
I’ve worked on a corporate project with multiple Java services, anon isn’t really exaggerating. Java can be a hell scape at times
taladar@sh.itjust.works 5 weeks ago
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.
HackerJoe@sh.itjust.works 5 weeks ago
Best with an old and vulnerable log4j on a Windows log server.
superkret@feddit.org 5 weeks ago
At that point, just kill the VM the app is running on and deal with the fallout.
RogueBanana@lemmy.zip 5 weeks ago
But none of this is relevant for a hello world programming, right?
scottmeme@sh.itjust.works 5 weeks ago
You would be surprised, errors right out of the box on a freshly initialized project aren’t uncommon
babybus@sh.itjust.works 5 weeks ago
As I’ve been working with Java professionally for years, you’re right, I would be surprised, because that would be really uncommon.