submitted 8 months ago* (last edited 8 months ago) by to c/asklemmy@lemmy.world
 

So, it seems like PieFed is becoming a real alternative to lemmy.

What are the differences between these two? From a tech perspective, and also morality/ethics, if you want. Any differences in vision for these services?

Say whatever is on your mind. I want to know.

On which one should we put our weight?

Edit: I will leave this post here, which is a post by one of the devs of Lemmy that enumerates some of the things Lemmy 1.0 has. Lemmy 1.0 seems to be already in alpha stage and is already testable. The feature selection does look fantastic. Here is the post I am referring to: https://lemmy.ml/post/40744781

you are viewing a single comment's thread
view the rest of the comments
[–] 18 points 8 months ago* (last edited 8 months ago) (3 children)

Piefed has some neat features unique to it, such as:

  • a very nice gallery view for image heavy communities.
  • the ability to combine comments from multiple communities under one post, if the same link was posted to all of them. You can see an example of that here (notice how the comments have dividers for each community).
  • the ability to create and subscribe to a pre-made list of communities, sorta like a multi-reddit.

On the sysadmin side of things, it'd bring some nice advantages regarding network resource usage and page loading speed, and benefits from using tried and tested industry standard frameworks (I.e, Flask), instead of bespoke solutions.

  • source
  • hideshow 3 child comments
  • [–] [S] 1 point 8 months ago* (last edited 8 months ago) (1 child)

    Page loading speed is interesting. Your link only tested on mobile. A few days ago I did a non-scientific test, on desktop, (just me browing on piefed) and I thought lemmy was faster. But I may be wrong, or it was just instance specific.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 8 months ago

    In most cases, when bandwidth/latency is not a bottleneck, the thing that limits page load times is the database (in both lemmy and piefed's case). So, if an instance has a beefy server they are running their db on, then it is going to snappier most of the time.

  • source
  • parent