this post was submitted on 11 Jun 2025
515 points (98.1% liked)
Fediverse memes
1483 readers
233 users here now
Memes about the Fediverse.
Rules
General
- Be respectful
- Post on topic
- No bigotry or hate speech
Specific
- We are not YPTB. If you have a problem with the way an instance or community is run, then take it up over at !yepowertrippinbastards@lemmy.dbzer0.com.
- Addendum: Yes we know that you think ml/hexbear/grad are tankies and or .world are a bunch of liberals but it gets old quickly. Try and come up with new material.
Elsewhere in the Fediverse
Other relevant communities:
- !fediverse@lemmy.world
- !yepowertrippinbastards@lemmy.dbzer0.com
- !lemmydrama@lemmy.world
- !fediverselore@lemmy.ca
- !bestofthefediverse@lemmy.ca
- !fedigrow@lemmy.zip
founded 8 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
And they want to migrate to piefed? Does it have better performance than Lemmy? That would be hilarious if python were faster than rust.
Anti Commercial-AI license
Tbh, the vast majority of performance issues don't come from the language but from the application itself.
While python is clearly slower than rust when it comes to pure native performance when doing exactly the same things exactly the same way and only within the language itself, the same isn't necessarily true in the bigger picture.
So independent of the programming language, investing time in optimizing can improve the performance much more than using a faster language, and it's much easier to make perfectly optimized high-level language code than perfectly optimized low-level language code.
Facts right here. I love Rust and my day job is Python. Neither is too slow for most of my use cases. Though one cool thing about Rust is the super low overhead. So well-written Rust, much like well-written C, is great for low-power devices. Still, the database is going to be memory, IOPS and maybe CPU hungry as it grows. You can optimize data structures, but you still need to read said data.
The main bottleneck is I/O anyway.
It is the medium term plan, yes (if feasible).
The user facing side of Piefed is more optimized for speed and low resource use, which fits well with our Solarpunk ethos, and on the backend side I expect it to be easier to maintain and the performance impact should be neglible as most of it is the Postgres database with Lemmy and likely Piefed as well.