Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove author's job search ad to conform with the new NPM policy #634

Closed
wants to merge 1 commit into from

Conversation

capaj
Copy link

@capaj capaj commented Aug 30, 2019

While I don't really agree with the new NPM policy as reported here: https://www.zdnet.com/article/npm-bans-terminal-ads/
I do think it could give grounds for removal/ban of this package. If this were to happen, we'd get another left-pad debacle.
So maybe let's remove this just to be on the safe side with NPM shall we?

While I don't really agree with the new NPM policy as reported here: https://www.zdnet.com/article/npm-bans-terminal-ads/
I do think it could give grounds for removal/ban of this package. If this were to happen, we'd get another left-pad debacle.
So maybe let's remove this just to be on the safe side with NPM shall we?

PS: If you have a tweet where you announce looking for a job or portfolio I'd be happy to share link to that on my social media.
@KaySackey
Copy link

If it becomes a left-pad debacle, they deserve it. Policies should feature thoughtful human moderation.

@zloirock
Copy link
Owner

If NPM will ban the postinstall message, it will be moved to browsers console. If NPM will ban core-js - it will cause problems for millions of users. I warned about it.

@milankragujevic
Copy link

If NPM will ban the postinstall message, it will be moved to browsers console. If NPM will ban core-js - it will cause problems for millions of users. I warned about it.

Acting in such a way will get you labeled a bully, which is a label that fits your behavior very well.

@dpikt
Copy link

dpikt commented Aug 30, 2019

So to clarify @zloirock - big packages don't need to follow NPM policy because they're "too big to fail"? And you would rather play a game of chicken, with thousands of people's work on the line, than delete your job posting?

@TrejGun
Copy link

TrejGun commented Aug 30, 2019

The problem is NPM are too greedy, they are earning money by hosting private packages but not letting people earn money on their platform as well. There is no button for donation, no subscription and no othey way to pay to author, so people have to use Open Collective and advertise in postinstall message to get some profit. This is the real problem you have to solve rather than blaim @zloirock for donationware.

@ryanelian
Copy link

ryanelian commented Aug 30, 2019

If NPM will ban the postinstall message, it will be moved to browsers console.

While I respect you for maintaining this package, this sort of behavior will get you burned by the community.

When you start injecting developers' apps with ads, your library WILL get forked.

@krainboltgreene
Copy link

@ryanelian "You'd better act servile or someone else will take on your massive work that you do for free!!!"

@transiient
Copy link

Wow, @zloirock, you act so entitled, it's shocking. No one who uses your packages owes you anything. If people wanted to donate to you for your work, it's their choice. You released free, open-source software, for the public to use without any financial obligation to you.

@krainboltgreene
Copy link

Christ @sam-cross, what a terrible opinion.

@transiient
Copy link

@krainboltgreene it's not an opinion, it's a fact. The package uses the MIT license which specifically grants the right to use the code "free of charge".

@TrejGun
Copy link

TrejGun commented Aug 30, 2019

@sam-cross you can use this software as is on use another one.... nobody owes you anything (c)

@transiient
Copy link

@TrejGun that's what I'm saying. I know I'm not owed anything - nobody on either side is owed anything. core-js is being offered as a FREE (to use) product. Anybody can use it. Some of my project dependencies probably rely on core-js, and for that reason I'm thankful that the developer has put so much of his time and energy into creating it. That doesn't mean I have to pay him for the time he spent creating a free software product.

@HeyBanditoz
Copy link

If NPM will ban the postinstall message, it will be moved to browsers console. If NPM will ban core-js - it will cause problems for millions of users. I warned about it.

So it seems the solution is to remove the offending code, right? Or are millions of users losing functionality not your issue?

@joshmanders
Copy link

@sam-cross if you don't like what the author and maintainer of this package puts into it, you have expressed permission per the license to fork it and maintain it yourself. Stop being an entitled brat.

@transiient
Copy link

@joshmanders oh stop it. I know that.

@slinkardbrandon
Copy link

If NPM will ban the postinstall message, it will be moved to browsers console. If NPM will ban core-js - it will cause problems for millions of users. I warned about it.

Good luck getting a “good job” with an attitude like that.

@melvincarvalho
Copy link

Used By : 3,416,052

Bruh

@ErikHumphrey
Copy link

If NPM will ban the postinstall message, it will be moved to browsers console. If NPM will ban core-js - it will cause problems for millions of users. I warned about it.

Good luck getting a “good job” with an attitude like that.

If I recall correctly, @zloirock has expressed in the past that he's received many good job offers, but is looking for a company highly dependent on core-js so that he can maintain it for them.

@mgalgs
Copy link

mgalgs commented Aug 30, 2019

Related: #635

@isaacs
Copy link

isaacs commented Aug 31, 2019

#635 (comment)

@zloirock zloirock closed this Aug 31, 2019
@zloirock
Copy link
Owner

Thanks for the PR. Seems it's not require, see @isaacs clarification.

Repository owner locked as too heated and limited conversation to collaborators Aug 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.