Fediverse

28750 readers

115 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 2 years ago

MODERATORS

[email protected]

363

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

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

309 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] 9 points 11 months ago

I am not a fan of Java. However, I think that you are 100% correct. This is a potentially very useful stack to have available and I hope that the two projects track together well.

This project has potential for high velocity development that Lemmy will never be able to match, purely because of the languages. Rust is, factually, slower to develop in than Java, even for experienced devs. Add to that the greater population that is comfortable with Java, and you have a recipe for really pushing interesting things and innovating quickly. Possibly establishing a relationship somewhat like Debian Sid to Debian Stable. It could also be interesting to have some low-level, Rust modules that are shared between the two when Lemmy gets to 1.0 (API stability), if there is something that is more optimally implemented in Rust but that would introduce more coupling.