• 61 Posts
  • 1.6K Comments
Joined 1 year ago
cake
Cake day: September 1st, 2023

help-circle
  • Is zig memory safe by design? If not, rust will “win”. Large companies aren’t going to hire for an unknown or unpopular memory unsafe language when they already have C or C++ - there’s just no contest.

    Last I read, zig didn’t even have a standard string library. Unless that changes, it won’t even be a viable alternative to C/C++.

    Edit: I checked and got this

    the Zig language, like C, entrusts memory management to humans, placing full trust in human development. Zig then provides some memory safety checks to ensure memory safety. However, it still lacks the strict compile-time guarantees of Rust’s ownership system and borrow checker. Therefore, when writing Zig code, developers need to pay more attention to potential memory safety issues and ensure that errors and exceptional situations are handled correctly.

    Rust Magazine

    Anti Commercial-AI license
















  • You’re missing the point. I don’t really care about Winamp. It’s ancient and probably used by about 15 grandpas. The point is the behavior of the people in the issues and pull requests. It’s possible to be polite, but firm and bring a point across. Right now it looks like a pack of dogs barking around thinking they’re witty and clever for doing so.

    Projects are not entitled to be received gratefully and respectfully if you treat open source devs like a disposable source of free labour.

    Nobody’s forcing anybody to do anything. You’re not forced to contribute in any way shape or form. Winamp hasn’t hired anybody there to write code under bad conditions. Justifying bad behavior “because the other side is doing it” (which isn’t true btw) is just weak.

    Anti Commercial-AI license