Every time I go to the piefed frontpage I'm blown away by how much more polished it is. It has all the bells and whistles that lemmy is sometimes missing.

Whats the catch? Why aren't we recommending everyone goes to piefed instead of lemmy?

App support is one thing I can think of.

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

[–] avidamoeba@lemmy.ca 39 points 3 weeks ago* (last edited 3 weeks ago) (29 children)

We have data on what it costs to run a sizeable instance of Lemmy and it's not a lot. How does Piefed compare? Anyone starting an instance who envisions it growing large has to contend with this question. Currently it seems it's got a bit under 1000 users across under 10 servers.

There are now sizeable communities run on Lemmy instances that are reinforced by network effects. There needs to be a significant reason for them to migrate. To that point, the collective project is building communities away from corporate power, not software. The software is a tool to facilitate that. Lemmy has worked well so far in this regard. If someone can show that Piefed can work better and not cost significantly more, it'll probably get adopted for new communities. If the difference is drastic, we may even see migrations from Lemmy.

[–] Sibshops@lemm.ee 11 points 3 weeks ago (8 children)

I second this. Lemmy is written in Rust where as piefed is written in Python. When it comes to running a high-performance webserver, Lemmy has the advantage.

[–] poVoq@slrpnk.net 19 points 3 weeks ago (4 children)

While theoretically true, the main bottleneck with Lemmy seems to be the database performance, so with both projects depending on PostgreSQL for that, I somewhat doubt that Piefed being written in Python will have much noticeable effect in reality.

[–] nickwitha_k@lemmy.sdf.org 3 points 3 weeks ago

the main bottleneck with Lemmy seems to be the database performance, so with both projects depending on PostgreSQL

Postgres being a bottleneck is a first for me. Not saying it's not possible, just... It's postgres. Wondering if it's more an issue with ORM, etc.

load more comments (3 replies)

load more comments (6 replies)

load more comments (26 replies)