this post was submitted on 15 Jun 2023
162 points (94.5% liked)

Programming

17402 readers
108 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

My first experience with Lemmy was thinking that the UI was beautiful, and lemmy.ml (the first instance I looked at) was asking people not to join because they already had 1500 users and were struggling to scale.

1500 users just doesn't seem like much, it seems like the type of load you could handle with a Raspberry Pi in a dusty corner.

Are the Lemmy servers struggling to scale because of the federation process / protocols?

Maybe I underestimate how much compute goes into hosting user generated content? Users generate very little text, but uploading pictures takes more space. Users are generating millions of bytes of content and it's overloading computers that can handle billions of bytes with ease, what happened? Am I missing something here?

Or maybe the code is just inefficient?

Which brings me to the title's question: Does Lemmy benefit from using Rust? None of the problems I can imagine are related to code execution speed.

If the federation process and protocols are inefficient, then everything is being built on sand. Popular protocols are hard to change. How often does the HTTP protocol change? Never. The language used for the code doesn't matter in this case.

If the code is just inefficient, well, inefficient Rust is probably slower than efficient Python or JavaScript. Could the complexity of Rust have pushed the devs towards a simpler but less efficient solution that ends up being slower than garbage collected languages? I'm sure this has happened before, but I don't know anything about the Lemmy code.

Or, again, maybe I'm just underestimating the amount of compute required to support 1500 users sharing a little bit of text and a few images?

you are viewing a single comment's thread
view the rest of the comments
[–] yourstruly@dataterm.digital 2 points 1 year ago* (last edited 1 year ago) (13 children)

Hear me out, but I believe that using Rust holds Lemmy back.

Writing Rust code is difficult, and fairly time consuming. It's difficult to get right, and as other commenters have noted, Lemmy code seems to do a lot of things for the "hype factor" (like Websockets). It's difficult to find enough devs as well.

The article about Discord switching to Rust from Go in the top comment is misleading in my opinion. They totally rearchitected their service while rewriting it, so it's an apples to oranges comparision.

[–] SomeGuyNamedMy@vlemmy.net 7 points 1 year ago (3 children)

If your college educated in cs, and your main issue with a codebase is the language its writen in, i have some serious questions as to how the hell you graduated

[–] Snickeboa@lemmy.world 6 points 1 year ago

Different languages do excel at different architectures / designs. Either through performance or how the code is written.

But yeah, sometimes people make too much of a deal of which language something is written in. And it becomes a discussion of trends or personal favorites instead.

I bet the hardest thing is finding devs who are actually proficient in Rust.

[–] lasagna@programming.dev 3 points 1 year ago

A rudimentary way to put it but ultimately correct.

Rust has already established itself as a solid language. That should be the first bell.

[–] psudo@beehaw.org 1 points 1 year ago

I mean most CS courses don't teach you to code or what a project should look like. It's why the mentality in most professional work is to pretty much forget everything you learned in college and you'll be trained on the job.

load more comments (9 replies)