358
Sublinks Aims to Be a Drop-In Replacement for Lemmy
(wedistribute.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Jan 2024
358 points (96.6% liked)
Fediverse
28518 readers
166 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 !moderators@lemmy.world!
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 2 years ago
MODERATORS
There is nothing inherently wrong with Java I would speculate, but it can be a royal pain in the ass to manage if you just need one application to work.
I know the basics of the language, but from what I have seen managing it, I don't like it. Just from being in security, I constantly hit barriers with devs because of versioning issues. There is always some ancient app running on a version of Java that can't be updated, for whatever reason. Version management is always a pain, but with Java? Goddamn.
I admit ignorance about the details of Java and how awesome it is for job security. There is no way in hell I could even debate anyone who has watched a single video on YouTube about Java. However, from what I have seen, it either works great or it fails explosively with billions of randomly allocated threads attempting to suck memory from every other server within 50 miles.
If it's awesome to code with, cool. I am just a little salty from my experiences, as you can tell.
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".