this post was submitted on 23 Jan 2024
360 points (96.6% liked)
Fediverse
28475 readers
804 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Java is also memory safe
After working in java for over a decade, I will never use another garbage-collected language if I can avoid it again. I still have nightmares about debugging memory build-ups and having to trace down where to do manual garbage collection. I remember my shop eventually just paid for 32 GB ram servers, and java filled those up too.
Rust doesn't have these problems because its not a garbage collected language like java or go, and has an ownership-based memory model that's easy to work with.
Is that still a problem in newer java versions? I have to admit I have only written simple things in java.
Garbage collection is by nature imperfect, its impossible for it to always be correct about when and what things to free up in memory. The best option is to not use a garbage collected language.
Wow. It's amazing that anyone ever got anything to work in java. Must have never got used for anything
Ah yes, that explains the log4j fiasco
That wasn't a memory safety issue, that was a what the fuck were you thinking design issue. It would have been batshit in any language