| 12 Nov 2024 |
 aidalgol | We were promised the inverse of Wine, and we were given just a different UI for the same hypervisor. Typical Microsoft. | 05:37:41 |
 gulbanana | * i'm using WSL2, although it's a shame that the WSL1 model didn't work out. it was a more novel tech | 05:41:28 |
 KFears (annoying) | WSL2 is a lot less exciting, yeah. Though, it's a much more practical approach I think. Not quite sure why WSL2 has so many odd specifics and compromises, though | 05:42:18 |
 tc424 (Steve D) | WSL1 was a bit more like CoLinux, I think? https://en.wikipedia.org/wiki/Cooperative_Linux | 10:59:28 |
 K900 | No, not at all | 11:05:41 |
| K900 | WSL1 was literally reverse Wine | 11:05:50 |
| K900 | CoLinux was basically running an entire Linux kernel in userspace | 11:06:51 |
 Linux Hackerman | My colleague ran into a problem with the lix installer and the issue submission URL gave back a 504, while the rest of git.lix.systems worked fine (about 90min ago). Was that forgejo being down temporarily and a cache serving stuff that can be cached, or is there something more Interesting happening here? | 15:30:48 |
|  sanketh (they/them) joined the room. | 18:52:40 |
| 13 Nov 2024 |
|  to-do joined the room. | 01:02:48 |
|  eein joined the room. | 17:59:51 |
|  night joined the room. | 19:59:09 |
| KFears (annoying) | In reply to @kfears:matrix.org
Just checked, seems to be a "yes" :( Huh, it is still the case. So bizarre | 20:14:31 |
| KFears (annoying) | Am I doing something wrong? The tree that is supposedly "missing" is consistently the same... | 20:15:06 |
|  Ty (they/them) joined the room. | 21:12:43 |
|  moved to @etherealconclave:myriation.xyz joined the room. | 21:25:17 |
| moved to @etherealconclave:myriation.xyz | this has probably been asked a million times already, but why exactly does lix exist? i read a bit about some drama with nix a few months ago, but there's nothing i can find that really explains what all the drama was, other than some partnerships (that some places said were cancelled and others said weren't) with military related companies, and something about a rules change (i think) that nobody liked? i'm honestly just confused | 21:28:09 |
| tc424 (Steve D) | I'm not an expert but I think there were much longer running issues, a big one being nixpkgs/nixos itself being stuck until very recently on an older version of nix because none of the newer versions were stable enough. | 21:29:12 |
| tc424 (Steve D) | So it's not just purely political - there are technical reasons as well, I understand. | 21:29:56 |
| moved to @etherealconclave:myriation.xyz | yeah, i saw something about that. i guess that makes sense | 21:30:26 |
| tc424 (Steve D) | There also seems to be a bit of conflict of interest these days as well, with some of the main/original nix devs having set up their own company and starting to produce commercial nix products. It makes it hard to tell whether bad decisions about the main project are being made inadvertently or deliberately. | 21:35:02 |
| moved to @etherealconclave:myriation.xyz | ah. that's no fun | 21:41:19 |
| moved to @etherealconclave:myriation.xyz | well, i guess another question that's probably been asked a lot: why isn't there an iso for lix? | 21:43:13 |
| K900 | Lix is just the package manager | 21:43:40 |
| moved to @etherealconclave:myriation.xyz | it seems like the closest thing to a "lixos" is telling nixos "hey, use lix instead" | 21:43:46 |
| K900 | There is no Lix distribution (yet?) | 21:43:51 |
| moved to @etherealconclave:myriation.xyz | ah, it's just the package manager | 21:44:08 |
| K900 | As for why Lix exists, it's really less about the one specific incident and more about the ongoing lack of governance in the larger Nix/NixOS/nixpkgs ecosystem | 21:44:35 |
| moved to @etherealconclave:myriation.xyz | i'm used to arch and whatnot, the package manager and the OS being called something very similar messes with me a lot | 21:44:52 |
| K900 | Well you'll be glad to know that if a LixOS were to one day exist, it would not be called LixOS | 21:45:34 |
