I was excited when I found out there was a link aggregator (read: I was obsessed with reddit-like forums) that divorced itself from the controversy or the alienating political idealogy of the lemmy developers.
However, other than that, I can't understand piefed.
-
The project seems unorganized. The first google result for "piefed" is the piefed.social instance and not about the project. I had to go to "About" then click on "PieFed" just to get to this link the project page. For lemmy? The first link about lemmy the project is about the project not an instance. Point to lemmy.
-
Lemmy uses rust which, like the main devs' political idealogy, may be polarizing (see Linus vs Rust Devs). Piefed uses, well, python. Yes, there is a learning curve to a new language, but rust is statically and strongly typed whereas python is duck typed. Also, it appears as though pip is one of the tools used in the installation which has been prone to supply chain attacks. Yes, more people know python. But that isn't necessarily a net positive and I wouldn't consider that if I were choosing the stack. Another point to lemmy (for me)
-
Piefed is on codeberg/forgejo. Lemmy is on github. Point to piefed.
-
Piefed doesn't have controversial devs (supposedly Lemmy does). Point to piefed.
So, as much as I want to like piefed, I'm having trouble really choosing it. Can someone add on why they use piefed over lemmy? I really want to like piefed.
They're different and have relative strengths and weaknesses. Despite being a contributor to piefed, I moderate a handful of communities on a lemmy instance and don't really have intentions of moving them. Overall, piefed is a lot less "mature" than lemmy, which makes sense because it is a lot newer of a project. It is getting better now about being more stable, but there are plenty of things that are still changing quite rapidly, especially on the api front.
As for python/pip/typing, I just don't see this as the major issue that some people seem to think it is. We aren't adding dependencies willy-nilly and the framework in which we are working (flask) is a very mature one that has stood the test of time. The fact that python is used for the project has tremendously helped the project in that it has allowed for a large number of contributions from many different people. Frankly, if piefed wasn't in python, it would not be nearly as feature complete as it is now thanks to the wide range of contributions we have received from folks.
How are the dependency upgrades handled?
I’d argue that a good design and tech stack that takes longer to be feature complete is better than a bad one.
Someone elsewhere said something along the lines of the issues are well managed. I think I need to look more at the quality of the code.
Thank you