{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicdzdzmcowj5dmxb3skrnpqe65jnrfzifsnnmgrzuwege3dfodwom",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mhfuf3y7bt62"
  },
  "path": "/t/ann-a-piece-of-flake-nix-repository/13812#post_2",
  "publishedAt": "2026-03-19T09:46:15.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "Nice project!\nBut I feel there are some gaps here:\n\n  1. Why is nixpkgs being big is a problem, github eats the hosting cost after all. Why do we care how much MS has to pay for it?\n  2. How flake solve the issues with nixpkgs being big? as far as I can tell, every flake I’ve seen uses nixpkgs. You’d need some way to bootsrap a nix ecosystem without nixpkgs. An indexing site doesn’t do this (although it may help with discoverability)\n  3. How flakes compose? As far as I can tell they don’t. An example of flake composition would be nice. Composition is the fundemental problem you need to solve to split up a big thing (nixpkgs) into smaller parts.\n\n\n\nI’m asking these questions so you can explain your project better.",
  "title": "[ANN] A piece of flake nix repository"
}