this post was submitted on 13 Nov 2024
794 points (96.2% liked)
Greentext
4383 readers
1383 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.