> But this is true for any solution, whether Nim script, Chocolatey, or else!
Yes, that's an argument for keeping the number of "official" ways to do something to a minimum, not an argument against Chocolatey in particular. > As I wrote, I was happy to contribute to the first "original" PowerShell > script (note the singular), and my proposal was centered around the idea that > the Choco package should be automated and self-update with new Nim releases, > requiring no further scripting. Yes but the work starts after the initial coding phase. It's not about replacing 0.16.0 with $version and have this script generated, that's indeed easy enough. It's about _maintaining_ this in the longer run. Issues might be reported, they need to be handled. The alternative ways to install Nim might grow a new feature (e.g. choose between Aporia and VS Code Plugin) and the Chocolatey package should support that too then. Also you have misunderstood me in various ways. I will accept such a PR, it's just that I am really skeptical.
