• 0 Posts
  • 727 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle








  • Computers are not a good choice for “regular users”. Get them a locked-down iPhone and be done with it.

    What you are describing is not a situation unique to Linux - or even Windows. “Software is hard and it sometimes breaks”. My Windows 11 laptop that I use for work and to which I have made exactly zero modifications sometimes doesn’t recognize when I’ve connected external speakers. And I can’t disable hyper-v despite following all of the instructions. This is a corporate provisioned and managed system and simple stuff just doesn’t work.

    X% of all things have bugs. Your mistake is in thinking that the percentage that you’re seeing are somehow special or related to the particular OS you’re running at the time. The classic “the grass is greener” fallacy. This is pretty evidenced also by the fact that you’re a classic “distro hopper” whose always looking for the perfect system rather than taking the time to understand the problems and deal with them as they come.






  • The thing is that, in C the API could be slightly different and you could get terrible crashes, for example because certain variables were freed at different times, etc. In Rust that is literally impossible to happen unless you (very extremely rarely) need to do something unsafe, which is explicitly marked as such and will never surprise you with an unexpected crash.

    What? That’s utter BS. Maybe the kernel devs aren’t wrong about the “rust religion”. Not every bug in C is a memory bug.

    We’re talking about a future version having regressions or different-than-expected behavior from what your application was built and tested on. I guarantee you that can happen with rust.