3 ms·
That question seriously resonated with me when I saw it raised in the GitHub thread. (https://github.com/standard/standard/issues/1381#issuecomment-524577750 ht
by brianpgordon 7y ago
That question seriously resonated with me when I saw it raised in the GitHub thread. (https://github.com/standard/standard/issues/1381#issuecomment-524577750 https://github.com/standard/standard/issues/1381#issuecommen...)
Any package which transitively includes `standard/standard` also inherits the advertisement. That would seem to suggest a kind of logic like "if people are going to use my work to help make their thing successful, it's only fair that I'm rewarded too." And that really does make sense. I could totally nerd out over the idea of a graph-based incentive structure, maybe implemented with a new crypto token for extra gee-whiz spiciness. If his prototype `feross/funding` package had been launched with a built-in technical mechanism for transitive profit-sharing I think the idea might just have been intriguing enough to distract from some of the appalling terribleness of embedding ads in package post-install messages.
- jwalton 7y ago> Any package which transitively includes `standard/standard` also inherits the advertisement. Fortunately there should not be too many of those. If you're using `standard/standard` to format your code, it should be in your devDependencies, so if your project relies on it, and I rely on your project, I will never see this ad. If this model were to take off, and, say, `lodash` included an ad, that would be a different story. You'd probably see the same ad a few times over in your `npm install` because you probably have more than one version of lodash in your dependency tree. But, I can tell you right now, if you put an ad in your package, I'm going to work pretty hard to remove your package from my dependency tree, and hopefully there are enough people like me to stop this from taking off. :P