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.
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.
Yeah, this would be my concern as well if I had to run it. Sure Python apps can be fast and most time is spend in IO, not compute, and if you’re running a profitable operation the exact cost of compute might not matter much. However if you’re running a non-profit service and you want it to be as dirt cheap as possible so it can be free for most users, then the cost of compute very much does matter.
If you want it to be “free to most users”, the cost of data storage and IO will completely dominate over the cost of CPU.
There are plenty of good arguments to prefer Rust over python for a distributed application, but “language efficiency” is not one of them.
Anyway, if you are biased in favor of Rust and want a decent argument to justify it, I will let you use ‘It’s easier to compile Rust to WASM and have the application run on the browser, while compiling python in a cross-platform way is a nightmare’, free of charge.
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.
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.
Postgres is so quick if you know how to use it…
You don’t even need to know how to use it very well, in my experience.