Post

there should be a thing that reads your package.json and charges you $5/month per dependency - you don’t /have/ to! you could set the price to $1 per employee! - and then holds the funds and sends it to the people who made the code you use to do business how is not doing this more sustainable

14/1/26, 2:13 am3 reposts16 likes

Stew O'Connor

@stew.casa

14 Jan

So if you had a language where you had to pay per dependency and one where you didn't, which one would you tend to use?

@ky.fyi

14 Jan

double-duty! helps fund open source projects *and* financially disincentivizes package bloat. i like

nateberkopec.bsky.social

@nateberkopec.bsky.social

15 Jan

what if I don't want your money?

KJS

@kjsingh.bsky.social

15 Jan

you can opt out - the funds get redistributed and you still get a big thank you card

nateberkopec.bsky.social

@nateberkopec.bsky.social

15 Jan

I would enjoy a thank you card, tbf

tater1337

@tater1337.bsky.social

14 Jan

literal enshitification

Justin Higgins

@justinprojects.bsky.social

14 Jan

`npm pay` when enabled, takes your $N/month and distributes it according to some rules you've setup. eg: the more times your npm installs packageXYZ, the more money it gets from your pool

Justin Higgins

@justinprojects.bsky.social

14 Jan

relies on existing `npm fund` discovery mechanism?

Techsticles

@techsticles.bsky.social

14 Jan

Do they then refund all of the money when their repo gets hacked?