!pbdtvoHxUGLhcEvnlu:nixos.org

Exotic Nix Targets

345 Members
106 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
25 Mar 2023
@matthewcroughan:defenestrate.itmatthewcroughan - nix.zoneYeah me neither, I'm just thinking there are no limitations and what the design would look like without limitations 12:51:41
@7c6f434c:nitro.chat7c6f434cI mean, I don't like NixOS modules for any of the other reasons either…12:51:59
@matthewcroughan:defenestrate.itmatthewcroughan - nix.zone to me, the perfect setup is nix running everywhere for every purpose, to keep everything isomorphic 12:52:00
@7c6f434c:nitro.chat7c6f434cI kind of want enough RAM to run Nix evaluation on almost everything, that's true…12:52:52
@7c6f434c:nitro.chat7c6f434cBut for many purposes I am mostly fine with Nix-on-whatever12:53:15
@7c6f434c:nitro.chat7c6f434c(Assuming a somewhat clueless but not too malicious and already platform-adapted carrier system)12:53:53
@matthewcroughan:defenestrate.itmatthewcroughan - nix.zone
In reply to @7c6f434c:nitro.chat
I kind of want enough RAM to run Nix evaluation on almost everything, that's true…
No I mean sharing eval cache would prevent that from being a problem, optionally
12:56:19
@matthewcroughan:defenestrate.itmatthewcroughan - nix.zonethere are ways we can keep it isomorphic just by messing around with caches and stuff, and fix these problems just like that 12:56:39
@7c6f434c:nitro.chat7c6f434cIf you give up on «actually can eval anywhere», I won't call Nix the ideal setup. Maybe looking at what Guix did, noticing it is still not the best direction, and designing a new Nix-like-tolerable-on-low-RAM without giving up on data-crunching-completeness…12:58:39
@matthewcroughan:defenestrate.itmatthewcroughan - nix.zoneI quite like the idea of hosting the top level closures somewhere like latest.mysytem.com and then having systemd pull it down on a regular basis and activate it13:01:24
@7c6f434c:nitro.chat7c6f434c(I am not saying I have a coherent vision how it would be, not yet)13:01:26
@matthewcroughan:defenestrate.itmatthewcroughan - nix.zoneThere's no nix involved in that13:01:29
@7c6f434c:nitro.chat7c6f434cWell, without Nix usable for configuration…13:01:42
@7c6f434c:nitro.chat7c6f434cI guess the next level is a cheap subscription service where you can fine-tune your system and add the closure to the update service… Given Nix deduplication, it won't scale too badly13:03:45
@matthewcroughan:defenestrate.itmatthewcroughan - nix.zoneI don't really get it, you can self host all this super easy13:04:59
@matthewcroughan:defenestrate.itmatthewcroughan - nix.zoneThe webroot of the system closure is one line of nix13:05:17
@matthewcroughan:defenestrate.itmatthewcroughan - nix.zonehttps://github.com/MatthewCroughan/nixcfg/blob/master/hosts/hetznix/modules/androidUpdate.nix#L813:05:38
@7c6f434c:nitro.chat7c6f434cWell, if you wanted to sell devices pre-flashed!13:05:39
@matthewcroughan:defenestrate.itmatthewcroughan - nix.zoneLike here's how I do the same for my robotnix device13:05:45

Show newer messages


Back to Room ListRoom Version: 6