HNHacker News
TopNewBestAskShowJobs

grhmc

2,440 karma · joined February 23, 2014

submissionscomments
grhmc··on Nix at work: FlakeHub Cache and private flakes
Ugh. I feel you. I think one thing that makes this hard is how big and intertwined Nixpkgs and NixOS is. All the modules are loaded all the time, and it can make the displayed errors propagate out to somewhere intractably far away from where the error actually is. There's a ton of work still being done in Nix to make that better, and I'm hopeful for an easier future :').
grhmc··on Parks on the Air
This is such a good and fun way to get in to radio. It is why I picked up my radio after being licensed, and inactive, for like ten years.
grhmc··on Nix at work: FlakeHub Cache and private flakes
> - Building our Go project in a Nix package was nearly impossible with private GitHub repos, so we moved on.

Yes. This is a nightmare, and is the literal step-one problem FlakeHub is designed to solve.

Regarding the monorepo causing big-bang updates that broke all your stuff: continued, strong, agreement. I think as nixpkgs continues to grow, and usage grows, we'll see a wider adoption of flakes from a pure "how do we all work together?" perspective. That's the flip side of FlakeHub's initial concept.

grhmc··on Nix at work: FlakeHub Cache and private flakes
Agreed. Thank you for saying so. We're working on this in two ways:

1. Reducing the number of moving parts, so there are fewer interfaces that need to be documented and understood ... because they don't exist.

2. Resources like https://zero-to-nix.com/, and https://docs.determinate.systems/.

This is a big lift, though, so anything we do here in the near future will definitely not be enough.

grhmc··on Nix at work: FlakeHub Cache and private flakes
Sure. To start with, we see flakes as stable as they are today: https://determinate.systems/posts/experimental-does-not-mean.... The ecosystem has broadly adopted flakes as their preferred way to use Nix, and we're standing by them and are committing to not breaking their flakes in the future.

On Monday, we launched Determinate Nix to help make this promise more real: https://determinate.systems/posts/announcing-determinate-nix.... Note: Determinate Nix is not a fork, it is a downstream. Our plan, and intent, is to keep all our patches sent to the upstream project first.

grhmc··on Nix at work: FlakeHub Cache and private flakes
There is a lot of turbulance in the project, but I think a lot of that is a natural result of twenty years of history meeting standout commercial success. Our approach here is to continue our pattern of improving Nix and sending patches upstream. We'll also continue improving the ecosystem around Nix, most of that being open source, and only a couple specific projects being proprietary.

Regarding the stability of the project: The project and distribution is incredibly vibrant, and not going anywhere. There are tens of thousands of organizations that depend on it every day, and projects that are funded on the time scale of decades. It's here to stay.

grhmc··on Show HN: Determinate Nix
Hey folks, CEO of Determinate here. I sent years as a Nix consultant, running into the very same problems over and over and over. Eelco and I teamed up to knock down those problems, and here is the first of a series showing what that means.

I'm here to answer questions!

grhmc··on Show HN: Flox 1.0 – Open-source dev env as code with Nix
DetSys founder here :). Firstly, congratulations to Flox on the launch.

DetSys is founded by Nix's inventor Eelco, and me -- a fairly long time community member (since ~2016.) We're also loaded with long term Nix users and contributors. We (the company) didn't invent flakes, and I didn't have anything to do with it either. While working at Tweag, Eelco worked with Target to develop the idea.

I'm not sure where this idea of bad blood or not contributing back comes from, either. The vast, vast majority of our code and products are completely FOSS, and our most popular product (the Determinate Nix Installer) is deliberately licensed in a way that upstream Nix can take it and integrate it however they want, any time they want. And I hope they do! We also invest heavily in contributions directly upstream. We're long time open source contributors and advocates, and that doesn't change now that we started a company.

I think there is a lot of compression of time and history here that has lead to lot of pretty baseless accusations and confusion. I think some people who don't like the change don't like it because they've built their own mechanisms to get what flakes provides. That's fine, nobody has to use flakes. The old ways aren't going away. Some folks don't like them because they're not technically perfect or bug-free. That's fine, too, but they're not becoming more stable by pretending flakes don't exist.

I look at threads like the one you linked as evidence we're doing something interesting. Nobody would care if what we were doing was useless.

One point that is absolutely true, though: DetSys is 100% contributed to the version of the future where Nix + Flakes is the thing. Flakes solve such vast problems that I feel there is no going back. This is the basis for the Determinate Nix Installer: we guarantee flake stability, and use the installer as the wedge to keep that promise with our users. This promise has been the basis of our work on FlakeHub and our just-launched-today FlakeHub Cache.

Unfortunately, nix.dev -- an official Nix documentation source -- specifically does not teach much about Flakes. To the degree of introducing documentation for unmaintained tools that see very low community adoption: https://nix.dev/guides/recipes/dependency-management.

We've taken a strong position on flakes by introducing our installer and zero-to-nix.com, a flake-first documentation source because of this confusion. I have asked numerous times for the various Nix leadership teams to make a choice on if flakes are the future or not, but as we can all plainly see: they have not chosen to do so. This confusion about flakes comes from the very top, unfortunately. I find this very motivating for building the best Nix company I can, to support the adoption of Nix and flakes in interesting places around the world.

grhmc··on Show HN: FlakeHub Cache: Fast, secure, configurable. A new take on Nix caching
> Am I missing something about how people are using flakes right now?

Yes. Lots of orgs are using Nix today and need to meet SOC2 or better, and are using many different caches to meet compliance objectives. This is creating a significant performance penalty.

Further, whether you care about the separation or not the onboarding process is simply nicer, because it is tied to the environment you're running in (GHA) not tokens you have to copy paste around.

> If I have a monorepo, flakes are likely off the table right away due to the performance hit.

If you've heard of "lazy trees", that work is being spearheaded by us at DetSys to address this problem :).

grhmc··on Show HN: FlakeHub Cache: Fast, secure, configurable. A new take on Nix caching
The problem people often run in to when persisting the nix store is that it can be very large, and updates often. This adds a significant tax on setup/teardown time and sometimes storage costs. The completely free and unsubsidized Magic Nix Cache's design alleviates that on GitHub Actions by persisting each path individually in the actions cache. FlakeHub Cache brings a for-cost component to that, which exposes the cache to your workstation and production infrastructure.
grhmc··on Show HN: FlakeHub Cache: Fast, secure, configurable. A new take on Nix caching
I'd love to find out how it compares! We're not quite ready to support CircleCI, but when we are -- want to do a test? You could hop on to our discord: https://determinate.systems/discord
grhmc··on Show HN: FlakeHub Cache: Fast, secure, configurable. A new take on Nix caching
Hey folks, DetSys's cofounder here. Eelco, the team, and I have been working hard on FlakeHub Cache for some time now. We're starting to round out the toolkit you need to take Nix to work. Here to answer questions!
grhmc··on Ask HN: Who is hiring? (February 2024)
Determinate Systems, Full time remote with overlap on New York TZ See: https://determinate.systems/

Determinate Systems is the Nix company, where cutting-edge technology meets unmatched expertise in Nix and flakes. We create the finest software development toolkit designed specifically for organizations that have embraced Nix and flakes. Our solutions are tailor-made for organizations prioritizing security and compliance, ensuring that software deployments are rock-solid and secure.

We're looking for our first frontend engineer, to work on Nix-centric projects like FlakeHub.com.

As a Frontend Engineer at Determinate Systems, you will be responsible for designing and implementing user interfaces for our web applications. You will collaborate closely with our cross-functional team to create seamless and visually appealing user experiences.

See: https://determinate.systems/careers/frontend-engineer

grhmc··on A new graphical installer for Nix on macOS
I'm really happy with how well this came out. Lots of new users who were intimidated by the CLI installer have started experimenting with Nix because of it. I'd be happy to answer questions about it!
grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
No, however because of the general requirement to use /nix/store as a prefix we do support using this method for avoiding global installations.
grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
Good thing we don't have anything for sale yet :').
grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
We don't need virtualization (that'd be easy.) We'd need mount namespacing and bind mounts to place a directory in your home directory at /nix during the process execution.

EDIT: User and process namespacing would help a lot as well, to improve build time isolation.

grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
> Unfortunately, it also still wants to make system-wide changes on macOS.

For context, these changes are:

1. Creating and mounting a volume at /nix for the store

2. A daemon used for isolating build environments

3. A zshrc / fish / bash hook to load a few environment variables (PATH, mostly)

4. (new!) an on-boot Launch Daemon to keep those profile hooks working between upgrades.

grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
Fair enough! Unfortunately that isn't likely to be true any time soon, since macOS doesn't offer the namespacing primitives necessary for that to be possible like it is on Linux. You can bet once it is feasibly a good experience, DetSys will be hot on its tracks to make it happen. Until then, then :).
grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
We wrote the Determinate Nix Installer with hopes that the greater project will adopt it[1]. Nix itself is fantastic. Improving the upstream Nix installer has been described as "unreasonably expensive and pointless"[2]. Hopefully it is adopted soon!

1. https://determinate.systems/posts/determinate-nix-installer

2. https://discourse.nixos.org/t/nix-survival-mode-macos-upgrad...

grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
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
grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
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 :(.
grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
Thank you a lot, pxc! I'm really glad you like it.
grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
Ah fabulous, thanks! I'll make a note internally. It'd still be great if you could open an issue.
grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
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 :).
grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
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

grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
This is just rolled out now! Sorry about that, I thought we'd hit merge on that PR before publishing :').
grhmc··on Nix Survival Mode: macOS upgrades won't break Nix anymore
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 upgrade of the installer's work itself ... but I'll put a ticket it! :)
grhmc··on Creating and modifying flakes using the FlakeHub CLI
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!
grhmc··on enron :: discover the power of WHY (2001)
Probably a good idea to hide 22 freak emails from a 22 year ol(d scandal.)
← PreviousPage 2 of 10Next →