• onlinepersona@programming.dev
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    1 hour ago

    Nix needs a typed language, better CLI interface, better documentation, a distributed cache, to to get rid of the monorepo / single source of control, to support different builders (aka not just bash), and have a less toxic community.

    For nix to be used by normal, non technical users, it must have a GUI. That is not optional.

    Nix could be great for a lot of things, but it’s not the only solution and won’t be the last.

    Anti Commercial-AI license

  • dinckel@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    5 hours ago

    The headline felt a little weird, but turns out this wasn’t written by Eelco. I thought how can they have found nix in 2016 if they’ve created it to begin with lol

    Either way, I’ve switched all by one of my machines to Nix now, including my Darwin laptop, and it’s honestly been pretty damn good.

    Aside from the huge learning curve, and a pretty depressing turnover rate for an occasional package update request, especially when it comes to home-manager.

    The ability to have a flake structure, that you can push to git, and then re-use on all of your systems, is huge.