> Often times they don't even have a project. Creating a .nimble file just to > play around with a package would be tedious.
it isn't, as long as it's just a nimble init away. AFAIK [stack](https://docs.haskellstack.org/en/stable/README/) and other modern build tools work this way and they're doing just fine; globally-installing packages is often regarded as a bad practice in other ecosystems as well. this post about cabal v. stack gives a good explanation [https://www.fpcomplete.com/blog/2015/06/why-is-stack-not-cabal](https://www.fpcomplete.com/blog/2015/06/why-is-stack-not-cabal) > Looking at an npm package for example, I see a similar command shown in the > right sidebar. that's not good advice, though: [https://www.smashingmagazine.com/2016/01/issue-with-global-node-npm-packages](https://www.smashingmagazine.com/2016/01/issue-with-global-node-npm-packages)/
