Robert Hensing

@kerckhove_ts @avi_press @domenkozar @fresheyeball I have not invested a lot more than source code contributions into the Haskell ecosystem, but in the Nix community I have spent way way more than I could justify even to myself, as someone who's passionate about the tech

@avi_press About being willing to pay money to save more money. I'm sure @domenkozar, @robert_hensing, @fresheyeball, etc will be able to confirm this.

Most of you will hate this idea, but if Hackage charged companies a small amount money to use the registry, it would easily fund a full time devops person for the HF, building better infrastructure for everyone.

Deliveries appear to have all caught up. Thank you @GitHubStatus!

@GitHubStatus Webhook deliveries towards @hercules_ci have stalled since 16:32 UTC, and the GitHub UI can not retrieve details of the latest few deliveries listed.

@GitHubStatus GitHub Webhook delivery to @Hercules_CI has stalled since around 16:32 UTC, and the GitHub Apps UI can not retrieve some of the latest hook details.

Re the open letter critical of Nix's governance (save-nix-together.org) and the Nix team (I have little insight into controversies elsewhere), I agree with everything @robert_hensing wrote in @roberth@functional.cafe/112332724870129421" target="_blank" rel="nofollow noopener">mastodon.social/@roberth@funct…

@sridca I would expect something to be posted here #commitcomment-132517786" target="_blank" rel="nofollow noopener">github.com/NixOS/moderati…

@sridca Unless the moderation team can provide more information, I see no sufficient grounds for a ban. While I may disagree with some of his political views, I find more concerning the mod's assumption that other assume ill from what they don't understand.

@alexelcu @sridca Am I wrong to believe that "touch grass" is often used in a condescending manner? This does not seem to be your intent.

@grhmc I said we're working towards actually sustainable and stable flakes, didn't I? Apparently strive was the wrong word. I've corrected that. Either this thread is too long, or you're not asking in good faith. I'll assume the prior and stop conversing.

@robert_hensing Good point, I'm not even asking for words about time or scope or plan, just if the team even *wants* flakes, and I still can't get a straight answer.

I'm surprised that a member of the Nix team -- ostensibly aligned on the adoption and stabilization of flakes -- is part of an effort to move away from Flakes in NixOS projects: github.com/NixOS/nix.dev/…

@grhmc "intends for flakes to be a stable feature". Nothing about time or scope. Now who's weaseling? I've said all there is to say. We may agree on more as a team, but I won't be pushing for anything. Would rather get shit done.

@robert_hensing What I'm hoping to hear is whether or not the nix team intends for flakes to be considered a stable feature of nix, and if the overall Nix team aligned on this being the goal. What I'm hearing is a lot of words about how flakes need work, but nothing concrete on my question.

@grhmc No critters were harmed during my tweeting. Flakes needs a bunch of work done before it's stable. Maybe that's what you need to hear? Re strive: change that to "work toward". Non-native speaker or whatever. Thanks.

@robert_hensing I’m can’t help but feel like you’re using weasel words here, like “strive”. Can you be straight with me? They’re not complicated questions.

@grhmc That is the future we strive for. Do remember that it is a large set of features that was apparently rushed and then effectively abandoned for various reasons we're not getting into. Also Nix promises reproducibility for non-experimental features, so this needs time / resources.

@robert_hensing No. My question is does the nix team intend for flakes to be considered a stable feature of nix? And: is the overall Nix team aligned on this being the goal?

@grhmc So we're not deleting flakes or anything.

@grhmc Unless you mean stabilizing the bugs or throwing reproducibility overboard, we are stabilizing the set of features that flakes consists of and builds on. Expect team based communications soon-ish.

@grhmc This is documentation team policy. The Nix team is not involved with this. You're reading too much into this.

At NixCon, I implored the Nix team to choose if they want flakes to be stable or not. I'm disappointed to see this happen without the team choosing one way or another.

@nixos_org @tweagio You might want to wait until the path not valid bug is fixed github.com/NixOS/nix/issu…

👏 Nix 2.18 is out! There are nearly ten new features and improvements that have been added, chack it out and share your feedback! buff.ly/3rncmcr

@mpeytonjones @hercules_ci @hercules_ci handles IFD well

@robert_hensing @hercules_ci Yeah, that's what I guessed. Just wondering how soon we can stop killing our hydra with IFD...

🧑‍🔬Nix 2.18 (unreleased) will launch a new experiment for accepted RFC 92: Dynamic Derivations Just merged it 🚀

@fmzakari There's the RFC, tomberek will give a talk at #NixCon. Maybe there's a document I'm not thinking of. It's new and we have yet to figure out how to use a feature like this in practice.

@robert_hensing Is there a good write up ? I'd like to understand how to replace 2nix tooling for Ruby or Python. I wonder if this can read BUILD Bazel files and also be used there too.

@samueldr @zimbatm @nixos_org I'd highlighted the phrases that stood out to me personally. The article: samuel.dionne-riel.com/blog/2023/09/0…

@zimbatm @robert_hensing @nixos_org “There is one thing I can say, though, is that we need to tread carefully and stabilize the features one at a time” is the conclusion to my post. Do read it if you still haven't :)

I strongly agree with @samueldr 's views on @nixos_org Flakes. "Anyone pushing for them to "just" be marked "stable" already does not appreciate the heavy meaning behind marking them stable" "Nix prides itself in still allowing many years old expressions to evaluate just fine."

@mpeytonjones Unlike import from derivation, this is feasible for hydra and the NixOS cache. Unfortunately Hydra reimplements certain logic, which has to be updated. Same for @hercules_ci for that matter.

@robert_hensing What's the compatibility story? Will stuff using this build on hydra etc?