• 0 Posts
  • 8 Comments
Joined 6 months ago
cake
Cake day: May 16th, 2024

help-circle
  • I could see that being a thing, but the line between the engine and the game itself is a bit blurry in this context. Copyrighting just the assets and content would often not be enough. There will always be a good chunk of game code which isn’t strictly part of the engine but under this model should remain closed source, otherwise people could just bring their own assets.

    Frankly I’d be satisfied with companies open sourcing their games after they stop supporting and/or selling them, mostly for preservation and all that. I think that would be a great middle-ground.





  • It’s not really the same thing though, those are filesystem snapshots, not package registry snapshots. Think of Nix generations as blueprints of how to construct your OS and environment, not the files themselves (though those are certainly required). I’m not quite sure how to explain it, but it’s a lot more powerful than what basically amounts to a backup.


  • Mia@lemmy.blahaj.zonetolinuxmemes@lemmy.worldHave you tried NixOS?
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    3 months ago

    Definitely more stable than Arch. Plus, you can easily roll back if something breaks, and you can choose which packages should use the unstable branch while keeping the overall system stable, which I find amazing. I don’t think I’ve ever had a breaking update, which I can’t say about Arch.

    The problem I have with Nix is that you can effectively forget about running random programs or GitHub projects. You either package everything the Nix way or nothing works. As a developer and someone who often likes to try stuff out, that’s really annoying. And Nix, the language, is ass, so is the whole build system. Nobody can convince me otherwise.