| 1 May 2022 |
 @blaggacao:matrix.org | Well, the flake.nix is a user flake. It needs to have a co.pat layer right there to work with colmena. | 21:24:01 |
| @blaggacao:matrix.org | std has no middle ware to do that conversion for the user. | 21:24:38 |
| @blaggacao:matrix.org | Essentially, std has just gotten rid of it's last compatibility layer that projected the schema onto something that nix itself requires. | 21:25:41 |
| @blaggacao:matrix.org | The reason is that rhe end user should also have a consistent view of the std mental model when entering the repl. | 21:26:17 |
| @blaggacao:matrix.org | The only way to communicate metadata in std is .#__std. | 21:26:37 |
| @blaggacao:matrix.org | (by design) | 21:26:46 |
 Zhaofeng Li | So you are essentially expecting all tools to be .#__std-aware (either natively or through some out-of-tree hackery like this), not the other way around. I'm not sure that this is a workable way forward. | 21:33:54 |
| @blaggacao:matrix.org | The problem with the other way round is that it very fundamentally breaks a homogeneous out-of-the-box experience.
std expects for it's purpose (and within it's boundaries) self.outputs to be it's exclusive domain.
It therefore expects all tools that it ships with to be schema neutral. | 21:39:53 |
| @blaggacao:matrix.org | If adapters are necessary, they can be done by the user via std.growOn. But the user has to conscientiously implement those adapters. | 21:41:07 |
| @blaggacao:matrix.org | So for an out-of-the-box experience, std expects tooling that it ships with to be flake schema-neutral | 21:42:52 |
| @blaggacao:matrix.org | std.grow, on the other hand, can't produce an output schema that doesn't correspond to the folder layout. | 21:45:16 |
| @blaggacao:matrix.org | In reply to @zhaofeng:zhaofeng.li
So you are essentially expecting all tools to be .#__std-aware (either natively or through some out-of-tree hackery like this), not the other way around. I'm not sure that this is a workable way forward. For clarification, that is actually not technically correct. .#__std is the mechanism by which metadata is transferred to the TUI, including actions. Those actions can transport an arbitrary command sequence. | 22:45:34 |
| @blaggacao:matrix.org | So these actions could just provide plain colmema commands with its built-in schema.
But then, I couldn't provide such actions out of the box, because they would depend on the compatibility layer, which is the user's domain. | 22:47:14 |
| @blaggacao:matrix.org | * So these actions could just provide plain `colmena` commands with its built-in schema.
But then, I couldn't provide such actions out of the box (for `copmena`), because they would depend on the compatibility layer, which is the user's domain. | 22:47:40 |
| @blaggacao:matrix.org | * So these actions could just provide plain `colmena` commands with its built-in schema.
But then, I couldn't provide such actions out of the box (for `colmena`), because they would depend on the compatibility layer, which is the user's domain. | 22:47:47 |
| 2 May 2022 |
 Wanja Hentze | Would you accept a PR to that effect, or do you prefer to do this yourself? | 13:13:52 |
| @blaggacao:matrix.org | Zhaofeng Li: I added a harvester: https://github.com/divnix/std/issues/60#issue-1223217085 for easier compat. But it still wouldn't accept to be system-neutral. That mapping is just too complicated. | 18:43:27 |
| 6 May 2022 |
|  @jeff:ocjtech.us joined the room. | 04:36:25 |
