Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> It's everyone's free choice whether they're willing to put their code out there and whether they're willing to actively maintain it for free once it's out there.

Literally not according to you. One 'git push origin master' and our contributor has signed up to your requirements.

Dominic made no promises to anyone -- he offered the world something and said they could use it if they wanted. Full stop.




> One 'git push origin master' and our contributor has signed up to your requirements.

I made no such claim. Did you read what I actually wrote?

> Dominic made no promises to anyone

Not by putting his code up on github, no. But that's not all he did.


> > Dominic made no promises to anyone

> Not by putting his code up on github, no. But that's not all he did.

I don’t see how putting your code on npm is fundamentally any different.

No one is entitled to free maintenance of gratis software forever, just because someone once said “npm publish”.

That’s not how open source works. It works by people contributing and getting involved, as opposed to entitled freeloading.


> No one is entitled to free maintenance of gratis software forever, just because someone once said “npm publish”.

I have made no such claim. If he didn't want to maintain it any more, he could have said "npm deprecate" and that would have been fine.

What's not fine is to say "npm publish", then actively maintain the software for years, then decide you don't want to any more (which, in itself, is fine, it's your choice how much effort you want to put in), but not tell anyone, not deprecate, not send any signal that you have changed your commitment to the package--and then hand over publish rights to some random person who emails you, also without telling anyone.

If you think that is fine, then, as I said several posts upthread in response to another poster, you've basically said no developers should ever trust npm, because people who say "npm publish" are making no commitment whatever, not even to say "npm deprecate" if they don't want to maintain the package any more, or to tell anyone if they decide to hand maintenance over to some other random person. That is not how open source works.


> you've basically said no developers should ever trust npm

Nobody should. At least not blindly. You should check what updates are and who made them. On every update.

Anything else is irresponsible and your own god damn fault when things go wrong.

> That is not how open source works.

npm is a proprietary package-repo and has nothing to do with how open source works. You can also easily publish proprietary packages using npm.


> Nobody should.

Ok, thanks for putting everyone on notice.

> npm is a proprietary package-repo and has nothing to do with how open source works.

So event-stream is not open source?




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: