Jacek Sieka

> One reason I see the global cache useful and pretty crucial is the CI use case. You don't want to do full nimble install every time for the ci...

> For nim I find it more beneficial as it's "package finding" logic will be completely stripped out from it. +1

https://github.com/ethereum/hive is the official upstream project for these kinds of setup - can we contribute there instead?

since this is in nim-libp2p and is called kademlia, it should reasonably implement and interop with upstream kad-dht as a first step - or we should move it to some...

what's the plan here?

`config.nims` is imo a strategic mistake that will keep creating problems and complexity for tooling, but indeed, since the codebase is already polluted with it, it might be the lesser...

> I might be missing a context, but why making NBS compatible with lock files given the fact that nimble is already a tool supporting locking files? 2 reasons: *...

> The problems you outlined can be solved by teaching Nim about lockfiles and how to locate package paths. the idea would be that `--noNimblePath` is the default (in a...

> The user would still face the problem that before the paths file is generated (or if it's outdated), nim and nimsuggest won't work as expected. For me, this is...

> Is this an approval :) ? it's not a disapproval - just like I wouldn't approve of anyone jumping off a cliff without appropriate gear, but can't stop those...