I'm not sure how to feel about this.<p>On one hand, it's an appealing way to manage dealing with different OS/Arch for a binary. On the other hand, this is not something I'd want to use in production, as it's very implicit. I'd rather explicitly call specific versions of installed binaries over implicitly call files installed in $DOTSLASH_CACHE (particularly if the binary is fetched on-demand).<p>This looks like it could be a useful tool in certain situations, such as shared/consistent dev environments. But generating the dotslash file (with hashes, urls, etc...) seems quite manual, which will limit adoption. In this way, it's not too different from traditional environmental module files, but it does automate a good chunk. If the main use-case is development, I'm not sure if this is better than devcontainers.<p>It seems like a useful tool, but I'm not sure where I'd <i>actually</i> use it. Maybe I'm missing the main use cases?
> executing a DotSlash file could "run anything,"<p><a href="https://dotslash-cli.com/docs/motivation/" rel="nofollow">https://dotslash-cli.com/docs/motivation/</a><p>Seems promising but obviously security around the dotslash file needs to be well thought out.