@flora_pm I want to know a network-amortized amount of dependency cost I would incur on my downstream if I add this one to my library.
`aeson` dependency list looks expansive, but the package can be reasonably expected to end up in pretty much everybody's cache anyway.
`lens` has quite a Kmettverse to it, but it is already used by a lots of other packages too.
Finally, `interpolatedstring-perl6` has a relatively tiny list, but one of the items is `haskell-src-meta` which is 1) a hog for compilation time and 2) is a relatively niche.
So, `aeson` is a relatively no-brainer to add.
`lens` is kinda okay.
But when selecting a text QQ package I'd rather peek around for a few more minutes.
@dpwiz Okay, we'd love to brainstorm that a bit. Would you mind opening a Discussion (github.com/flora-pm/flora-server/discussions/new/) with the criteria you have in mind? :)