Comments by "dkosmari" (@dkosmari) on "Massive Memory Leaks in System76's Cosmic Desktop (Written in "Memory Safe" Rust)" video.

  1. The thing is, Rust bet everything on one kind of guardrails, and oversold it as if it would deal with a lot of problems. Rust bloggers love to use broken C code mixed with C++ code, to show "the Rust version is better," but it only shows they're either dishonest, or very incompetent.
    74
  2. It's okay, there will be new "perfect language" product launched next month, and these "developers" jump on the bandwagon again. EDIT: please update us, a week from now, about the amount of salt this video generated. Publish the downvotes and hatemail this video generated. Remember kids, salt only makes rust worse.
    39
  3. Back in the day, Java programmers would brag about how Java programs could be just as "fast and efficient" as C programs when managing memory... if you had at least 7x more memory than your Java program needs. These delusional "engineers" have been around for along time.
    35
  4. And on top of that, memory is just one type of resource that can leak, among many others.
    22
  5. The fact that you group C and C++ in this imaginary "C/C++" language makes everyone else glad you love Rust so much. Please don't ever leave Rust.
    17
  6. I feel so safe when I stare at an out-of-memory kernel panic in my computer. It's very useful.
    12
  7. No computer is as safe as when it crashes with an Out-Of-Memory kernel panic.
    12
  8. The majority of the vitriol we get from Rust cultists is how wonderful it is at handling memory, including avoiding memory leaks. In the "The Rust Programming Language", 15.6, it claims that its wonderful memory safety guarantees "make it difficult" to have memory leaks. The harder you backpedal now, the harder we will laugh at you.
    11
  9. Nice backpedaling. Here its, from the "The Rust Programming Language" book: "Rust’s memory safety guarantees make it difficult, but not impossible, to accidentally create memory that is never cleaned up (known as a memory leak)." You can't just pretend you never heard this bogus claim about memory leaks in Rust. Mald and dilate.
    9
  10.  @zyxzevn  You can do the same in C, using `malloc()` and no `free()`. Memory safety has never been easier!
    7
  11.  @yoeight  Mald and dilate.
    5
  12. Gnome Shell is implemented in JavaScript. I don't see JavaScript programmers bragging about how their magic programming language solves memory problems. In fact, most JavaScript programmers are so ashamed of their own language, they say "I'm a Node.js programmer."
    4
  13. Good question. Look up what Linux (the kernel) does by default, when it enters an out-of-memory state: it kills random processes to try and free up some memory. If you're very lucky, the process that was just killed can be restarted later with no major consequences. But if there's a process that's ever consuming more and more memory, no process can be ever restarted. So by the time you can manually kill the leaky process, the entire system can be in such a bad state, it might not be responsive anymore. Now imagine the program you just had to kill, is talking directly to your GPU through Wayland and OpenGL/Vulkan, and it left the GPU locked up. Whilst the kernel can clean up memory after killing a process, it's much harder to reset hardware back to a working state.
    3
  14. With all the salt coming out of this story, it will only rust harder.
    3
  15. Rust programmers earned every bit of hatred and mockery they get.
    2
  16.  @monkev1199  Show us one example.
    2
  17. There is some fault of the language too, when the language fails to provide the proper tools for solving the problem. In the "The Rust Programming Language" book, they brag about how hard it is to leak memory in Rust. They deserve every bit of mockery they're getting. A language that makes it a hassle to deal with problems, is guilty of making the problem worse.
    2
  18. But for the wrong reason though.
    2
  19. Did you choose a gender for today?
    2
  20. They hired a bunch of Rust programmers. Can't fire them now, it will kick a storm of "anti-transgender" articles against them.
    1
  21. @ How many genders are there?
    1
  22. This story is not about memory leaks. It's about Rust developers getting a good dose of reality, and hopefully making them shut up about Rust's "magic solution for memory problems." They're already backpedaling, saying they never made any claims about memory leaks, as we couldn't just find them on the top of the search results.
    1
  23.  @nozwock  Read the "The Rust Programming Language" book then, instead of Wikipedia. Go to 15.6. It outright says, the memory safety guarantees help dealing with memory leaks.
    1