In many ways they already are ahead. The front end is a bit wonky though, and some of the foundational features are still catching up (it’s fully functioning though).
For one thing, they have “categories” of communities, and for another I can block all users from any instance I choose - though there is really no easy way to accomplish that while still on Lemmy proper.
But like when you upvote something, later it remembers that but won’t show you the color. The interface is really pretty though, and solves several of the issues I had with Lemmy, like another one is that you can turn on viewing or both the upvote and separate downvote counts, which for Lemmy iirc you can only see that for comments, but for posts that only shows on the mobile site yet not on the desktop for some reason.
The PieFed devs are super responsive, quite extraordinary so imho. It’s like they care or something (uh… cause they do, ofc!:-).
So especially since Lemmy is not perfect either, check out both Mbin and PieFed and just see them in action without an account, just for the fun of it.:-)
The DB is all that matters. Python can scale very well through parallelization. So long as one doesn’t restrict themselves to one process, there’s really little chokepoint.
Nope… CPU and memory usage matter as well… if they get exhausted, you get throttling. This also has an impact on server-costs… Why run 2 instances of something that serves 4k requests/second over one instance that serves 9k/s (just an over-exaggerating example)
That’s why I say if you don’t restrict to single process. As to why something which might be slightly more inefficient (it’s not going to be that much), it’s because of ease of development and pool of potential developers to help you with it.
In many ways they already are ahead. The front end is a bit wonky though, and some of the foundational features are still catching up (it’s fully functioning though).
For one thing, they have “categories” of communities, and for another I can block all users from any instance I choose - though there is really no easy way to accomplish that while still on Lemmy proper.
But like when you upvote something, later it remembers that but won’t show you the color. The interface is really pretty though, and solves several of the issues I had with Lemmy, like another one is that you can turn on viewing or both the upvote and separate downvote counts, which for Lemmy iirc you can only see that for comments, but for posts that only shows on the mobile site yet not on the desktop for some reason.
The PieFed devs are super responsive, quite extraordinary so imho. It’s like they care or something (uh… cause they do, ofc!:-).
So especially since Lemmy is not perfect either, check out both Mbin and PieFed and just see them in action without an account, just for the fun of it.:-)
There’s no way Python and Flask are going to scale as well as Rust. It’s going to require more hardware to run and be able to handle fewer users.
The DB is all that matters. Python can scale very well through parallelization. So long as one doesn’t restrict themselves to one process, there’s really little chokepoint.
Nope… CPU and memory usage matter as well… if they get exhausted, you get throttling. This also has an impact on server-costs… Why run 2 instances of something that serves 4k requests/second over one instance that serves 9k/s (just an over-exaggerating example)
That’s why I say if you don’t restrict to single process. As to why something which might be slightly more inefficient (it’s not going to be that much), it’s because of ease of development and pool of potential developers to help you with it.