Lemmy Project Priorities Observations

5 readers

1 users here now

I've raised my voice loudly on meta communities, github, and created new [email protected] and [email protected] communities.

I feel like the performance problems are being ignored for over 30 days when there are a half-dozen solutions that could be coded in 5 to 10 hours of labor by one person.

I've been developing client/server messaging apps professionally since 1984, and I firmly believe that Lemmy is currently suffering from a lack of testing by the developers and lack of concern for data loss. A basic e-mail MTA in 1993 would send a "did not deliver" message back to message sender, but Lemmy just drops delivery and there is no mention of this in the release notes//introduction on GitHub. I also find that the Lemmy developers do not like to "eat their own dog food" and actually use Lemmy's communities to discuss the ongoing development and priorities of Lemmy coding. They are not testing the code and sampling the data very much, and I am posting here, using Lemmy code, as part of my personal testing! I spent over 100 hours in June 2023 testing Lemmy technical problems, especially with performance and lost data delivery.

I'll toss it into this echo chamber.

founded 1 year ago

MODERATORS

[email protected]

08-30 (bulletintree.com)

submitted 1 year ago by [email protected] to c/[email protected]

1 comments fedilink hide all child comments

top 1 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 1 year ago

"This is how the Fediverse works. There is so much bad practices, so much haphazardly implemented functionality and so much bad API documentation all over the place that I wonder why nothing has extremely exploded so far." - Dirk at lemmy.ml

Dirk's comment is from hee: https://lemmy.world/post/4128651

Dirk is from Germany, not American like I am - and joined the same server I did - creating this site. The core developers left lemmy.ml crashing for months - now it's working better because there is less activity - not because the code scales and is improved.

The terrible SQL from Rust and Diesel was why I never opened shop. I knew lemmy.ml was online for over 4 full years..

Another new front-end was the 2023 priority from all this. July 11 is when they started: https://github.com/LemmyNet/lemmy-ui-leptos

When a dozen independent projects are building front-end apps, the people with over 4 years of experience with the code take all that back-end experience and bottle it up. Instead of actually improving documentation and API testing surface... WITH ALL those YEARS of experience... off to start a new Rust-centered project. The advantage being that Rust can use the same Rust objects... but that doesn't do anything for the front-ends that don't use Rust, the smartphone apps, etc.