News for hackers. Stuff that matters.
Re:Nix Team Creation by rgoulter on Wednesday October 05, 2022 @01:38PM (#33098699)
> Should I use flakes or not? Every single library I find is a Nix Flake, but insists that Flakes are experimental.

In this case, "it's experimental" should be read as "maybe the team will decide to make changes", rather than "it's not going to work half the time".

e.g. one change they made was changing the property "defaultPackage" to "packages.default".

(Anyway, the UX improvements from flakes are good, that once you've got the boilerplate, flakes are amazing).

> Nix is technologically sound but is struggling organizationally from its explosive growth

Well, that's the opposite problem of 'floundering'.

Re:Nix Team Creation by striking on Wednesday October 05, 2022 @02:21PM (#33099270)
> In this case, "it's experimental" should be read as "maybe the team will decide to make changes", rather than "it's not going to work half the time".

In that case, I can't in good conscience recommend we use such a feature at my workplace. We can't afford huge breaking changes, which is what that flag suggests. Which means my workplace is stuck with a bunch of `shell.nix` and `direnv` magic instead of clean flake-based envs.

It's not enough to gate features behind a flag, unless your only audience is enthusiasts. Versioning your features makes them accessible to a wider audience and encourages more risk-averse folks to adopt the features despite the possibility that they may undergo slight changes.

Re:Nix Team Creation by colinsane on Wednesday October 05, 2022 @04:12PM (#33100713)
> Versioning your features makes them accessible to a wider audience and encourages more risk-averse folks to adopt the features despite the possibility that they may undergo slight changes.

just pin the nix package itself and that should ensure the flake API remains consistent for however many months/years you want?

Re:Nix Team Creation by striking on Wednesday October 05, 2022 @04:38PM (#33100994)
That creates risk when we decide to upgrade, should bugs be fixed or new tools be implemented. Right now we are up to date and hope to keep it that way.
Re:Nix Team Creation by rgoulter on Wednesday October 05, 2022 @10:27PM (#33103622)
> That creates risk when we decide to upgrade, should bugs be fixed or new tools be implemented.

This is true of literally any dependency, though.

Semver is supposed to grant you confidence that things won't change very much, but it's not a technical guarantee.

In terms of "risk of adopting nix flakes", the lion's share of the risk is in "adopting nix" (because nix is difficult, hard to find people well versed in nix, etc.). The risks from adopting flakes on top of that are marginal.

Re:Nix Team Creation by colinsane on Wednesday October 05, 2022 @09:20PM (#33103227)
sure, there’s risk in any direction.

> Which means my workplace is stuck with a bunch of `shell.nix` and `direnv` magic instead of clean flake-based envs.

if flakes win out, this other stuff might well be deprecated someday. timeline for that is probably lengthier than the timeline where flakes don’t win, but it’s still there. in either scenario you’re gonna have a month or more between one approach being deprecated and being dropped altogether (6 months if you’re on the stable channel). you’re implicitly betting for or against the success of flakes here, weighted by the cost of refactoring should you bet on the “losing” side plus maintenance until the winner emerges. you describe non-flake maintenance as being higher cost, so from the outside it just feels like a suspicious bet to make.

Re:Nix Team Creation by hakre on Wednesday October 05, 2022 @02:58PM (#33099818)
AFAIK you don't have to use flakes. Same as it's fine to only use shell.nix. No system is for eternity, nix builds are deterministically cached, often never reproduced, so I see no strong arguments against using direnv with shell.nix.
Re:Nix Team Creation by striking on Wednesday October 05, 2022 @04:03PM (#33100616)
No, we don't have to use them, but they have lots of advantages and lots of support from the community that we just can't tap into.
Re:Nix Team Creation by Arcuru on Wednesday October 05, 2022 @04:09PM (#33100679)
The Nix team doesn't allow any community proposals for making changes to Flakes because it is still 'experimental' and hasn't yet gone through an RFC. So it's 'experimental' in the sense that it might change, but the people who have suggested changes to the design are generally told that they won't discuss changes because it's not yet stabilized.

That kind of circular reasoning seems problematic.

Don't get me wrong, I like flakes, I use them for my NixOS setup, but the way that flakes development has been handled is very concerning.

Re:Nix Team Creation by rgoulter on Wednesday October 05, 2022 @10:23PM (#33103586)
> The Nix team doesn't allow any community proposals for making changes to Flakes because it is still 'experimental' and hasn't yet gone through an RFC.

You sound like you have something particular in mind.

If I look at the Nix RFCs, flakes was as RFC 0049 https://github.com/NixOS/rfcs/pull/49

Maybe Alyssa's comment here? https://github.com/NixOS/rfcs/pull/136#discussion_r987278726

Re:Nix Team Creation by nvln on Wednesday October 05, 2022 @01:45PM (#33098802)
> Well, that's the opposite problem of 'floundering'.

+1. The explosive growth has resulted in organic blossoming of several new ideas, approaches and templates. Not all of them are great and it takes time to sift through them to see if there are canonical approaches.

The creation of the team to streamline these ideas, bless some official paths is well timed.

Re:Nix Team Creation by nonbirithm on Wednesday October 05, 2022 @02:19PM (#33099248)
>> Should I use flakes or not? Every single library I find is a Nix Flake, but insists that Flakes are experimental.

> In this case, "it's experimental" should be read as "maybe the team will decide to make changes", rather than "it's not going to work half the time".

This I think is part of the problem. People see the "experimental" label and don't understand that it's not "experimental" in the sense they're used to. Maybe labeling flakes as a "beta" feature and featuring the documentation more prominently would ease the confusion.

Re:Nix Team Creation by parminya on Wednesday October 05, 2022 @02:57PM (#33099813)
Even better would be just committing to what's there - it's so widely deployed that it's not seriously problematic. It's there to be used.
Re:Nix Team Creation by colordrops on Wednesday October 05, 2022 @03:02PM (#33099880)
Agreed, they should just bite the bullet and commit to flakes as enabled and not "experimental". There are plenty of other things that break regularly with my nix deployment and it's never flakes.
Re:Nix Team Creation by 0x457 on Wednesday October 05, 2022 @04:09PM (#33100674)
Well, it is experimental. Experimental rarely means "It's not going to work and might delete your data" that what, ironically, alpha and beta mean.
Re:Nix Team Creation by hakre on Wednesday October 05, 2022 @03:00PM (#33099843)
Perhaps the script is missing that declares what is undefined behaviour in flakes.
Re:Nix Team Creation by ruuda on Wednesday October 05, 2022 @04:33PM (#33100940)
The new Nix command syntax that was there up to 2.3 was always marked as experimental, but it worked fine for many years, I used it in many projects ... until it got deleted and replaced with flakes. I really hope they don't do that again. Flakes are de facto adopted by now, if they break it once more, it will fragment the ecosystem. Though there are rough edges where a breaking change would be beneficial in the long run.
Re:Nix Team Creation by thomastjeffery on Thursday October 06, 2022 @09:45AM (#33108072)
> In this case, "it's experimental" should be read as "maybe the team will decide to make changes", rather than "it's not going to work half the time".

This is exactly the clarification that needs to happen. It hasn't yet, and we've been needing it. That's what I mean by "floundering". Nix isn't broken, but its development progress has been needing explicit direction and clarity.

That's why I'm excited to hear a team is being put together. This is a great opportunity to bring some decisiveness into Nix's development.