Scoop let's you define package repositories (buckets) in a simple JSON format, whereas Chocolatey requires a NuGet v2 feed. Chocolatey imposes a hard request limit to their public repositories, so you can't use it for production without hosting your own repository. If you read this comment and you are looking for a tool to provision software to Windows-machines in a Linux-style manner, save yourself some time and choose scoop.
That is a significant point about production use of Chocolatey. Thank you for mentioning this, as I did not in the article. This is a positive point for Scoop.
Scoop let's you define package repositories (buckets) in a simple JSON format, whereas Chocolatey requires a NuGet v2 feed. Chocolatey imposes a hard request limit to their public repositories, so you can't use it for production without hosting your own repository. If you read this comment and you are looking for a tool to provision software to Windows-machines in a Linux-style manner, save yourself some time and choose scoop.
That is a significant point about production use of Chocolatey. Thank you for mentioning this, as I did not in the article. This is a positive point for Scoop.
There are, of course, various editions of Chocolatey that can help with this, if you have some money to spend.