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

help-circle



  • My immediate thought was: why not NixOS as a base? Building KDE is such a nightmare that if they had to deal with it themselves on NixOS, it would help them clear up their dependencies. Right now it’s such a big mess of unnamed and implicit dependencies that exposing it to the team would also show them how to cut down on them.

    My hope was also that if the KDE team were invest in a NixOS offshoot, that the OS would finally get proper GUIs or integrations into existing GUIs like Discover (why not Diskover?) Or the system settings and other config management.

    But, to be fair, I could understand if they considered it, took one look at the documentation and noped out.

    Anti Commercial-AI license


















  • 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