| 28 Jan 2026 |
Coca | pinning inputs and schemas are two pretty different things for a single tool to handle, so most focus on one or the other | 12:20:30 |
niko ⚡️ | What do you think npins is lacking in? | 13:12:25 |
niko ⚡️ | Or, well, what in your eyes warrants a successor. Because I can only think of inputs list vs lockfile not being separate files being a tiny bit annoying, but that's about it? Probably my usecases aren't sophisticated enough though | 13:13:44 |
piegames | That's the main point, yes | 13:14:36 |
piegames | But also, anything wanting ti replace flakes should also do transitive dependency resolution in some way | 13:15:00 |
piegames | In reply to @coca162:matrix.org pinning inputs and schemas are two pretty different things for a single tool to handle, so most focus on one or the other Yes but in the end we need a tool that combines both, one way or another | 13:15:23 |
niko ⚡️ | But then we're stepping out from just input locking to full on dependency management, probably also requiring standardized way of handing inputs and stuff like that. On one hand I agree but on the other my immediate reaction is "that's out of scope and I like how every projects brings their own locks and I don't want to extend the scope" | 13:19:59 |
Coca | It's almost certainly out of scope for npins, but hopefully at least for people who want to take a crack at making the combined thing they can use something like libnpins to at least not have to reinvent the wheel again | 13:24:05 |
raitobezarius | speaking of dependency management | 13:37:54 |
raitobezarius | https://zulip.lix.systems/#narrow/channel/10-Flakes/topic/.5BRFC.5D.20Allowing.20new.20installables.20syntaxes.20in.20nix3.20CLI/with/5152 — interested in opinions :) | 13:38:04 |
niko ⚡️ | Wow I was like "damn lix zulip looks pretty barren..." nope, it's just the ios app is broken and doesn't allow joining channels so all this time I only saw general | 13:54:51 |
niko ⚡️ | This is embarrassing | 13:54:57 |
raitobezarius | ^^ | 13:55:02 |
raitobezarius | That's good feedback for the Zulip team | 13:55:08 |
raitobezarius | They're usually quite interested | 13:55:11 |
raitobezarius | I think the onboarding story on mobile apps sucks a bit (even on desktop imho) | 13:55:29 |
raitobezarius | New channels gets created all the time and people doesn't see them necessarily | 13:55:36 |
niko ⚡️ | Now I need to go through all the other zulip servers I'm in on desktop and see what I missed all this time I only checked zulip on mobile | 13:56:05 |
piegames | In reply to @raitobezarius:matrix.org New channels gets created all the time and people doesn't see them necessarily Yeah, my main gripe with Zulip is that it isn't "all channels are visible by default" like Discord | 14:15:39 |
piegames | Even Matrix at least has "recommended channels" | 14:15:57 |
piegames | In theory we could just subscribe everyone by default when creating a new channel but that might have fucky consequences | 14:16:31 |
raitobezarius | conversely | 14:16:58 |
raitobezarius | if all channels were visible by default in certain servers, this would probably be very overwhelming | 14:17:10 |
raitobezarius | but i think this needs to be an onboarding decision | 14:17:15 |
raitobezarius | like you decide the experience you want | 14:17:20 |
raitobezarius | (for example, the rust-lang one) | 14:17:30 |
Lotte (it/its)/Cinny (she/her) θΔ& | larger discord servers also tend to hide channels by default | 14:17:56 |
niko ⚡️ | At least on discord you're very clearly informed of other channels existing | 14:18:59 |
niko ⚡️ | And when a new channel pops up you're prompted of its existence and can decide whether to follow it or not. Which could still be too overwhelming for something like rust zulip, but idk | 14:19:38 |
raitobezarius | on zulip too, new channels can be optionally announced in the main channel | 14:46:34 |