grhmc

9 ms·

31.
by grhmc 2y ago
Thank you, we will! =). I think there is a lot of opportunity here around a cohesive workflow around Nix. That is a big part about what I was consulting on for so many years. Maybe check out our demo on our home page: https://det
32.
by grhmc 2y ago
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 wher
33.
by grhmc 2y ago
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.
34.
by grhmc 2y ago
> - 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
35.
by grhmc 2y ago
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 h
36.
by grhmc 2y ago
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'r
37.
by grhmc 2y ago
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 ups
38.
Nix at work: FlakeHub Cache and private flakes(determinate.systems)
34 points by grhmc 2y ago|29 comments
39.
by grhmc 2y ago
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.
40.
Show HN: Determinate Nix(determinate.systems)
6 points by grhmc 2y ago|1 comments
41.
Fully Automated Nix Installation for macOS on AWS EC2(determinate.systems)
1 points by grhmc 2y ago|0 comments
42.
Solving corporate TLS certificates for Nix on macOS(determinate.systems)
3 points by grhmc 2y ago|0 comments
43.
Prepare Nix for macOS Sequoia(determinate.systems)
2 points by grhmc 2y ago|0 comments
44.
by grhmc 3y ago
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 contrib
45.
by grhmc 3y ago
> 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 significan
46.
by grhmc 3y ago
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 Magi
47.
by grhmc 3y ago
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
48.
by grhmc 3y ago
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!
49.
Show HN: FlakeHub Cache: Fast, secure, configurable. A new take on Nix caching(determinate.systems)
65 points by grhmc 3y ago|25 comments
50.
by grhmc 3y ago
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 creat
51.
Wikipedia: Spacecraft Cemetery(en.wikipedia.org)
2 points by grhmc 3y ago|0 comments
52.
by grhmc 3y ago
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!
53.
What we learned from installing Nix one million times(determinate.systems)
3 points by grhmc 3y ago|0 comments
54.
NixOS project adopts Contributor Covenant 1.4(discourse.nixos.org)
2 points by grhmc 3y ago|1 comments
55.
by grhmc 3y ago
No, however because of the general requirement to use /nix/store as a prefix we do support using this method for avoiding global installations.
56.
by grhmc 3y ago
Good thing we don't have anything for sale yet :').
57.
by grhmc 3y ago
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
58.
by grhmc 3y ago
> 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 / f
59.
by grhmc 3y ago
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,
60.
by grhmc 3y ago
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

More ›