this post was submitted on 29 Oct 2026
144 points (100.0% liked)

Programming

29080 readers
321 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] xmo748@programming.dev 3 points 1 day ago (1 children)

Clearly, but it's worth pointing out that this kind of problem isn't uniquely fixed by "just use Rust".

[–] thingsiplay@lemmy.ml 2 points 1 day ago (1 children)

I never said that only Rust prevents this. I just said using Rust in the Kernel would have prevented this issue.

[–] xmo748@programming.dev 2 points 1 day ago (1 children)

Fair enough. Don't you think it simplifies the issue a little bit? How long would it take to rewrite the entire TCP stack in rust?

[–] thingsiplay@lemmy.ml 1 points 1 day ago

I don't think a rewrite in Rust is necessary for everything that has a bug. Instead fixing the bug is probably more secure, before such alternative Rust code is mature enough to replace it.