Skip to content

no mentioning of technical limitations of nix and flakes design #4

@matu3ba

Description

@matu3ba

Not sure, where these points would belong best. Some are fundamental (unfixable) problems, others chosen tradeoffs chosen for (relative) portability across unixoids.

Namely for nix:

  • moving files into immutable nix store instead of creation of overlayfs due to posix performance and nesting limits
  • namespace control tools
  • package categories (missing metadata)
  • portability
  • debugging experience (tooling, documentation, best practice)

see also https://blog.wesleyac.com/posts/the-curse-of-nixos

Namely for flakes:

  • dependency explosion problem
  • system deps not inheritable
  • slow for big repos
  • no integration into nix ecosystem
  • no way to add dependencies from outside git repo without git repo

see also https://discourse.nixos.org/t/experimental-does-not-mean-unstable-detsyss-perspective-on-nix-flakes/32703

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions