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]

2023-08-23 (bulletintree.com)

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

3 comments fedilink hide all child comments

ORM and SQL .. I mean it's lived up to the bad side of the reputation.

It hides it. As someone said here:

I hate ORMs with the fury of a thousand suns. The problem is that I know SQL but now I have to spend a bunch of time trying to figure out how to convert SQL into ORM X just so it can convert it back to inefficient SQL. SQL mostly translates between various databases but ORMs are unique and you have to learn a new API for each one.

I'm on a project using TypeORM and it has been fantastic at helping developers on my team make really bad schemas due to not understanding how to use TypeORM to make the right relationships.

Currently I'm looking at pg-types because you just write SQL and it just helps by making some TypeScript types for you.

(I have used ORMs in C#, PHP, and JavaScript and I hate all of them)."

https://news.ycombinator.com/item?id=27547163

top 3 comments

sorted by: hot top controversial new old

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

I've used Reddit since it basically came online, and Usenet, Slashdot, Fark before that.... I didn't use Digg much, I was on Reddit before the Digg migration.

I think 2023 has hurt the think I actually grew to like the most about Reddit...

Google Search + Reddit

In protest, a lot of long-term accounts on Reddit deleted their comments and postings, so it isn't what it was last year.

It's sad to face that that era may never really return, I think the Twitter changes and Reddit API was all about keeping content away from ChatGPT... and search engines.

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

404: TypeError: Cannot read properties of undefined (reading 'replies')

lemmy.world throwing this just on routine home page. It's been this way since I started visiting in May... and I can crash a single-user server pretty easily by matching the number of communities and posts in the database. IT isn't DDOS, it's bad SQL.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

posting a day later, but I'm probably not going to keep posting daily any more.

This was posted 3 hours ago on Lemmy.world: 35 upvotes currently. https://lemmy.world/comment/2762900 and local copy: https://bulletintree.com/comment/2237045

"Let me be real. I never noticed outages stopping. It feels like it’s daily, I’m used to it, but I think it happens so often that lemmy.world has lost its growth opportunity, and we alienated the normies. I’m still going to stay on Lemmy, and I believe you’re doing the best you can, but we lost for the time being, the migration to Lemmy from Reddit is stunted."