Sender | Message | Time |
---|---|---|
14 Feb 2025 | ||
raitobezarius: cool I think it makes sense, and is a good policy to do what is right for the project no matter who is using it, nor how much money they have, etc. Maybe there are some companies who would reject that. But there are others that would not. Also some of the people talking to me are just people and not companies, etc. fwiw personally I hope Lix continues to be this way, and continues to succeed and grow without changing this aspect. I think the kinds of questions I was asking are good, and that it can be useful to answer them. But lix as a mostly volunteer open source project doesn't owe anyone any answers to these questions, nor does it owe guarantees or any other outcome other than what you all decide together to commit to, whatever that may be. Never the less I appreciate the answers that people offered here. And I'll be sure to include that there is an intention to like what you describe above. I feel that is important for people to understand if they want to use, contribute, etc so I will pass that aspect along as well | 22:23:49 | |
I appreciate the https://lix.systems/team/ conflict of interest statements too. Sets a better example, and this problem grew out of control in some ways in the Nix community. People who were trying to lead should have been doing that. | 22:28:12 | |
In reply to @samrose:matrix.orgmy reason for choosing Lix as a user (and I expect many people have similar reasons) is that CppNix had a long-standing bug with no effort being put into fixing it. Lix, sanely being forked from CppNix 2.18, was able to avoid this. I have my own personal opinions on the actions of members of the CppNix team, but the truth is Lix functions for me and CppNix does not. | 22:57:49 | |
I had heard a lot about this. I had not personally run into it. But I am also not building either all of nixpkgs, or combinations of things that surface the bug(s). But this is certainly important information for people who are comparing these things from stability etc points of view. | 23:24:47 | |
In reply to @samrose:matrix.orgLix is faster and has better error messages, and will improve even more on both in the next releases | 23:26:42 | |
That's my one-sentence selling pitch, at least | 23:27:04 | |
i mean, my personal problem was that nix flake update literally didn't work at all | 23:52:25 | |
which was because of this issue | 23:53:14 | |
but nix bugs have resulted in the fileset library from being banned from nixpkgs because they have to constantly work around these issues | 23:54:30 | |
15 Feb 2025 | ||
lol, never seen this one before | 00:27:47 | |
my code here would probably recurse infinitely if there wasn't a length check lol | 00:29:13 | |
hm, this is probably a stupid question, but can the keys/names in an attribute set be of any type other than string? or are only strings allowed? | 01:03:31 | |
{ 4 = 7; } doesn't work for example and i've never seen anything other than strings for keys, so i would assume they have to be strings, but i thought i'd double check | 01:04:26 | |
they are always strings | 02:13:53 | |
Redacted or Malformed Event | 02:27:23 | |
* Hey gang, what are the suggested ways to set up a Digital Ocean droplet? I know that I could use nixos-infect , nixos-anywhere or "${nixpkgs}/nixos/modules/virtualisation/digital-ocean-{config,image}.nix but I can't really decide on what I should attempt. | 02:27:41 |