4 ms·
Interesting idea, but I'm not sure that the automatic allocation model would make logical sense for many of my projects. Some of my dependencies are complicate
by kube-system 4y ago
Interesting idea, but I'm not sure that the automatic allocation model would make logical sense for many of my projects.
Some of my dependencies are complicated, critical, high-maintenance parts of my application, some are convenience wrappers for other more important sub-dependencies, and some are basic helper dependencies. Some are independent volunteer projects, and some are maintained by commercial companies by developers on salary. And some of them are libraries for services that I already pay for, like aws-sdk.
I don't think I could use something like this unless I can tweak the allocations.
- qwerty3344 4y agohttps://news.ycombinator.com/item?id=32841229 https://news.ycombinator.com/item?id=32841229 touched on this also, auto allocation would lead to disproportionate allocation for basic helper deps
- nevernude 4y agoOn an individual level allocation may seem a bit lopsided but, in aggregate, useful and popular projects will receive more funding. Commercial projects can either not claim their funds (which will be reallocated), or elect to pass their funds through to their dependencies. You also always have the option to explicitly list your dependencies.
- black_puppydog 4y agoIn aggregate the stripe and react dependencies in the example on the page might receive a pretty huge chunk and I'm not sure the stripe api should be funded by donations.
- nevernude 4y agoIf stripe doesn’t want to participate (likely) their funds are reallocated. They also have the option to pass on funds to their dependencies
- capableweb 4y agoSo users of Stripe SDK ends up donating to Stripe SDK that reallocates those funds to the dependencies that makes the Stripe SDK possible to build, rather than Stripe donating money directly to those dependencies that makes it possible for them to build their SDK? I'd rather fund libraries that don't have huge companies behind them, and those companies should donate themselves to the dependencies they use, so I can spend my money on donating to libraries I depend on directly.
- jonnycomputer 4y agoHonestly, it doesn't seem that hard to add blacklists, even category based ones.
- armini 4y agoValid point about tweaking allocation, I don’t think React/Facebook needs more money compared to some other projects. Check out https://thanks.dev/ https://thanks.dev/ they have a similar solution but allow allocation control.
- ChrisMarshallNY 4y agoI could see current higher-level projects taking advantage of their "first in line" access to the subscriptions. I could also see people writing "wrappers," and intercepting the top-level contribution, then skimming a bit off the top, before sending them on. Face it. There's money to be made, and a lot of really smart folks, with no ethics whatsoever, are more than willing to go for it. They'll figure out how to game it. The bottle has been uncorked, and the genie has escaped. There's no putting the candy back in that piñata.
- nevernude 4y agoWe thought long and hard about how people could game the system but ultimately it will be quite difficult because you still have to convince a large number of developers to actually use and depend on your project. And since the flow of donations and dependencies is public, the community will not look kindly one individuals trying such tactics.
- ChrisMarshallNY 4y agoFair 'nuff. I sincerely hope it works out. I have become somewhat cynical, and maybe that colors things.
- slekker 4y agoLovely username
- dcow 4y agoI'm not sure if you caught it but stackaid contributions trickle down. So, while `aws-sdk` gets a top-level cut of your donation, all of its dependencies, and so on, get cuts too. Also, flip the consideration, why is it fair that you only support a hand-curated list of projects and ignore the thankless dev writing all the little helpers and utilities that save you time over and over again? The blog post on their monte carlo simulations are pretty interesting. You can see how the funding ends up getting distributed, which is much like funding is today where people pick and choose, but with a healthy long tail that supports all the overlooked dependencies. What I really like about this approach is how egalitarian it is. If this catches on (and I believe it will) it's a self-contained ecosystem with its own incentives and emergent behavior. It even creates a healthy incentive for projects to minimize dependencies. And a high profile commercial project might want to signal virtue by passing on its pool entirely to its dependencies. Or maybe it claims its pool and pays it out as a bonus to the team that maintains the project? Or maybe it claims the pool and uses it to fund the infrastructure and operating costs and the price of the product you already pay for goes down. The possibilities are pretty fascinating. What stackaid presents is a solution for devs and organizations who recognize how much value their dependencies provide and want to spend more than $0/mo to support them but don't want to think too hard about it beyond that. I've been waiting for a solution like this for a long time, and I'm keen to participate!
- RussianCow 4y ago> Also, flip the consideration, why is it fair that you only support a hand-curated list of projects and ignore the thankless dev writing all the little helpers and utilities that save you time over and over again? There are lots of reasons. Maybe the project in question has a low impact to you, such that not having it wouldn't affect you very much. Or maybe it's something that's easy enough to write yourself and you just haven't done it because you haven't needed to. Or maybe there's a commercial alternative that's better but you just haven't needed to pay for it. You can't pretend that all of your dependencies have the same impact on your product. With that said, I think this is a great experiment, and I'm all for incentivizing devs to use fewer dependencies!
- 4y ago