| 24 May 2021 |
Regnat | Ah John isn’t there | 14:04:23 |
| Jez (he/him) left the room. | 14:04:43 |
| anderscs joined the room. | 17:11:24 |
| jul1u5 removed their profile picture. | 20:05:07 |
| infinisil joined the room. | 20:30:04 |
| lukebfox joined the room. | 22:34:47 |
| 25 May 2021 |
vika (she/her) 🏳️⚧️ | just an idea that popped into my head... a scratch dialect that compiles to NixOS configs! probably way too crazy but it just occured to me that NixOS modules could be represented as blocks and used in visual programming! For example, there could be a block that creates a new module, and blocks that get inserted inside, setting options to values declared by inner blocks. I'm not well-versed in Scratch but I think such a visual programming tool could help people understand Nixlang better | 11:03:45 |
vika (she/her) 🏳️⚧️ | Something like this (excuse my crappy ASCII art):
[NixOS module]
\- [option-set services]
|- [option-set redis]
| \- [option enable]
| \- [boolean true]
\- [option-set nginx]
\- [option enable]
\- [boolean true]
would compile to something like this:
{ config, pkgs, lib, modulesPath, ... }: {
services = {
redis = {
enable = true;
};
nginx = {
enable = true;
};
};
}
| 11:09:02 |
vika (she/her) 🏳️⚧️ | then all we need would be to just provide some sort of index on the options that would get consumed by the tool to show completions for the option-set which produces an attribute set | 11:09:53 |
vika (she/her) 🏳️⚧️ | i'm pretty sure this is a crappy idea and it has some sort of fatal drawback, I just haven't found one | 11:11:20 |
toonn | I think the only drawback is what happens with scratch too. You basically flatten the lowering curve a bunch but only at the start, creating a cliff. / -> _| | 11:48:18 |
toonn | This is brought up each time and then people say perfect shouldn't be the enemy of better. But I haven't seen anyone completing such an effort. | 11:49:12 |
toonn | It's usually brought up in the context of having an easier installer. Where you tick a bunch of boxes rather than having to write the entire configuration.nix. | 11:49:56 |
| 26 May 2021 |
| immae changed their display name from immae to immae (he/him). | 10:13:12 |
| Jonas Chevalier joined the room. | 11:03:00 |
| justinrestivo joined the room. | 12:27:49 |
| qbit joined the room. | 12:53:49 |
| infinisil changed their profile picture. | 16:51:14 |
| 27 May 2021 |
| Robert Hensing (roberth) joined the room. | 09:31:27 |
| konfou joined the room. | 11:34:36 |
| 6d03 joined the room. | 17:16:16 |
qbit | A few people have put together some patches to make nix build on OpenBSD, obviously nothing works after it's built and installed.. but it's a start! | 21:25:35 |
qbit | what would be next after that? stdenv? | 21:25:55 |
qbit | sterni had mentioned cross-compiling, but I am not smart enough to know how that would help :D | 21:26:39 |
| ldesgoui joined the room. | 23:18:43 |
| 28 May 2021 |
andi- | qbit: perhaps try to bootstrap some compiler toolchain based on a bootstrap seed. What is OpenBSD using for that usually when bootstrapping their compilers? | 00:17:18 |
| ash (it/its) 🏳️⚧️ joined the room. | 02:03:49 |
| djanatyn (they/them) changed their display name from djanatyn to djanatyn (they/them). | 11:31:12 |
qbit | good question. | 13:04:12 |
qbit | my understanding is it uses itself | 13:04:43 |