grhmc

17 ms·

1. 61.▲
   by grhmc 3y ago

   I don’t think that’s quite true, though I noticed Eelco didn’t mention Furlani’s work in his 2006 phd thesis on Nix (started in 2003): https://edolstra.github.io/pubs/phd-thesis.pdf
2. 62.▲
   by grhmc 3y ago

   Luckily newer builds of nix can be made statically that live in ~ and use namespaces to make it work. However, that doesn’t work on macOS at all :(.
3. 63.▲
   by grhmc 3y ago

   Thank you a lot, pxc! I'm really glad you like it.
4. 64.▲
   by grhmc 3y ago

   Ah fabulous, thanks! I'll make a note internally. It'd still be great if you could open an issue.
5. 65.▲
   by grhmc 3y ago

   That issue is exactly what we've fixed in this release of the Determinate Nix Installer, though, so if you use it today you should be covered for future upgrades :).
6. 66.▲
   by grhmc 3y ago

   Hmmm... would you mind opening an issue over here[1]? We have seen some related issues that might dovetail nicely. 1. https://github.com/determinateSystems/nix-installer
7. 67.▲
   by grhmc 3y ago

   This is just rolled out now! Sorry about that, I thought we'd hit merge on that PR before publishing :').
8. 68.▲
   by grhmc 3y ago

   Yeah, this is unfortunate. We've built the Determinate Nix Installer to be super reliable and safe. We've built the receipt mechanism to have very clear and safe "revert" phases. This has made it hard to architect an upg
9. 69.▲
   Nix Survival Mode: macOS upgrades won't break Nix anymore(determinate.systems)

   117 points by grhmc 3y ago|107 comments
10. 70.▲
    by grhmc 3y ago

    With FlakeHub, we're working hard at DetSys to make flakes as easy and natural as possible. Our additions to `fh` take a bite at that. I'm here for questions!
11. 71.▲
    by grhmc 3y ago

    Probably a good idea to hide 22 freak emails from a 22 year ol(d scandal.)
12. 72.▲
    Experimental does not mean unstable: Our perspective on Nix flakes(determinate.systems)

    4 points by grhmc 3y ago|1 comments
13. 73.▲
    by grhmc 3y ago

    Hey HN, after we launched FlakeHub last week, a common question was: what about the CLI? We heard you loud and clear, and here's a scrappy first pass at a useful fh CLI tool. It supports searching and adding inputs to your flake, plus
14. 74.▲
    Show HN: fh, the FlakeHub CLI(determinate.systems)

    5 points by grhmc 3y ago|1 comments
15. 75.▲
    by grhmc 3y ago

    I totally agree. This is one of the reasons we made FlakeHub, to make a better update mechanism that was flexible and supported things that aren't just github as sources. I think that'll happen, it'll just take a bit of time,
16. 76.▲
    by grhmc 3y ago

    Thank you, you're welcome! I think those tools are interesting, but a crutch / tape over difficulties that Nix presents. I think that tools that try to hide a bad experience with another layer often presents more problems in surpr
17. 77.▲
    by grhmc 3y ago

    I hope there will be, but I'm not really sure. I think the future of Nix is in smaller, focused flakes being shared and exchanged. People dunk on projects like Rust and Node for having infinity dependencies, but it is that way because
18. 78.▲
    by grhmc 3y ago

    This is a deeper cut of pretty foundational stuff. Almost no user will need to actually interact with schemas, and instead will use schemas provided by other folks. In other words, if this doesn't make sense: don't worry, you don&
19. 79.▲
    by grhmc 3y ago

    Hey folks, this is Graham -- CEO of DetSys. Happy to help answer any questions!
20. 80.▲
    by grhmc 3y ago

    Very cool! You can get nixpkgs unstable like this: nixpkgs-unstable.url = "https://flakehub.com/f/NixOS/nixpkgs/1.*.tar.gz";
21. 81.▲
    by grhmc 3y ago

    These are indeed valid concerns, and I think that it’s fair for the community to be vigilant about such things and to ask probing questions. But my perspective is both: - Nothing we’re doing is inherently proprietary or "secret sauce&q
22. 82.▲
    by grhmc 3y ago

    It's a tradition in the NixOS ecosystem, like nixos.com. (drat.)
23. 83.▲
    by grhmc 3y ago

    My feeling is we’ve been careful and considered about what we build and why, though I understand some folks don’t like what we’ve made. That’s their right, just like it is our right to build things we think are important and add value to th
24. 84.▲
    by grhmc 3y ago

    We strongly value open source software through and through, and have a team of long term contributors to open-source projects and communities. Part of open source is being allowed to build and experiment and see what happens. I find it unfo
25. 85.▲
    by grhmc 3y ago

    I know folks have anxieties about commercial investment, and anxieties about developing flakes. Whenever we hit bugs in flakes, we go work upstream to fix them. We do this rather often :). I won't try to persuade you one way or another
26. 86.▲
    by grhmc 3y ago

    That's largely right. Getting semver version solving into Nix core itself is a goal of ours. FlakeHub implements it server-side because landing it in Nix without proving it out conceptually would be really hard, and also -- in my opini
27. 87.▲
    by grhmc 3y ago

    I'm so glad you think so! We sure agree :). We're hoping this mechanism helps get some predictability, like that all the platforms that are listed fully evaluate as expected.
28. 88.▲
    by grhmc 3y ago

    In our opinion, flakes are the future of Nix and we're doing the hard work of using them extensively everywhere we can. While we do that, we fix bugs and papercuts along the way. I don't think flakes _can_ meaningfully stabilize w
29. 89.▲
    by grhmc 3y ago

    I just posted a reply on Discourse ( https://discourse.nixos.org/t/introducing-flakehub/32044/14?... ) but for posterity: I’m sorry some folks aren’t excited about FlakeHub, but that is okay. We’ve made it beca
30. 90.▲
    by grhmc 3y ago

    Thanks for sharing! We'll take a look. If nothing else, I'm sure you'll be able to publish using a CLI + token. Thanks!