this post was submitted on 23 Jan 2024
363 points (96.7% liked)
Fediverse
27910 readers
3 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
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
Legacy Java software is a massive pain in the ass. No arguments there. I’ve been migrating an app from Java 11->17 for the last 2 months and it’s a versioning mess. So many libraries deprecated and removed that don’t have easy replacements.
It’s great because things don’t break when they’re running, but the problem is upgrading.
Version management does seem to have become better with the last couple versions
(Confirmation bias, ENGAGE!)
We have a few of those projects coming up as well. Thankfully, I just get to poke at the apps to make sure the issues are resolved.
But yeah, one of my examples of rogue threads is a coding issue, not inherently a language issue. Even log4j issues can't be completely blamed on Java "The Language".