Fediverse

28223 readers

334 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

[email protected]

362

Sublinks Aims to Be a Drop-In Replacement for Lemmy (wedistribute.org)

submitted 9 months ago by [email protected] to c/[email protected]

310 comments fedilink hide all child comments

Seems like an interesting effort. A developer is building an alternative Java-based backend to Lemmy's Rust-based one, with the goal of building in a handful of different features. The dev is looking at using this compatibility to migrate their instance over to the new platform, while allowing the community to use their apps of choice.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 10 points 9 months ago (2 children)

Java is also memory safe

[–] [email protected] 2 points 9 months ago (1 children)

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.

[–] [email protected] 1 points 9 months ago (1 children)

Is that still a problem in newer java versions? I have to admit I have only written simple things in java.

[–] [email protected] 1 points 9 months ago (1 children)

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.

[–] [email protected] 1 points 9 months ago

Wow. It's amazing that anyone ever got anything to work in java. Must have never got used for anything

[–] [email protected] -1 points 9 months ago (1 children)

Ah yes, that explains the log4j fiasco

[–] [email protected] 1 points 9 months ago

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