[actionowl]

His tone is all wrong here:

> You really don't need to respond to repeat what every other poster is saying.

Obviously they did need to because no one from the team had responded yet. Also his response without any link to track the status is rather disappointing but entirely what I'd expect from the NPM team.

[jchw]

>his response without any link to track the status is rather disappointing but entirely what I'd expect from the NPM team.

Unfortunately, agreed. I hate being pessimistic but nothing disappoints me more than the way NPM handles a problem.

It's clearly not just a fluke at this point.

[btown]

Contrast this to Yarn’s response, also this holiday weekend, to an outage incidentally caused by the NPM team. https://github.com/yarnpkg/yarn/issues/5885#issuecomment-392... Professional, responsive, not afraid of blowback from accepting feedback and “+1” posts. Is there any reason to lock the post besides bruised ego and overwhelming phone notifications? Neither of those is justifiable when you’re emitting teapot errors because you implemented a spec wrong. This feels very indicative of a toxic, amateur culture, and perhaps we’ve let it operate our package infrastructure for too long.

[tracker1]

I'm actually blocked by the main person behind NPM because I disagreed with him over a politically motivated tweet he made... so it wouldn't surprise me in the slightest.

[booter12]

I was wondering how far down I would have to scroll to find something like this.

The guy is a total political zealot who hates corporations and hates that npm had to become one. He presented this at the end of NodeConfEU17 and also took the opportunity to lecture us (in Ireland) for being too white and not being as "diverse" as he wanted us to be.

IIRC, more than 50% of the presenters were women which he says is the only reason he attended the last day to speak at us. Great.

Hearing him talk was like someone taking a shit on the floor after an otherwise wonderful conference. It makes me cringe that I have to use npm after hearing that guy talk. I am not even sure I will go to that conference again after that.

[pluma]

Looks like his talk wasn't recorded[0]? He published the slides but they're sadly not very informative[1].

To be honest I can't believe the registry is still using CouchDB under the hood. It's not a good fit for the problem space.

I'm also not surprised he says this in his talk:

> Ultimately, I don’t like anyone else having control. If I’m going to give npm to a company, I want control of the company.

The npm registry and client should be controlled by a foundation for all the same reasons Node is. Yarn was a great step in that direction but it seems npm Inc is doubling down and based on how communication between the yarn maintainers and npm Inc went when they accidentally broke yarn[2][3], it feels like they're trying to fight yarn rather than cooperate.

I've seen npm Inc employees (including "community managers") attack people ("paying customers") on Twitter in response to criticism of how npm Inc runs their open source projects. They also don't seem to make any distinction between personal opinion and representing npm Inc, pretty much dot-com era startup "bro culture" but with different social politics.

[0]: https://www.youtube.com/playlist?list=PL0CdgOSSGlBaxNkrUIHrh...

[1]: https://www.dropbox.com/s/9rx9aalvts60w5y/why-npm-inc.pdf?dl...

[2]: https://twitter.com/jamiebuilds/status/1000198463269699584

[3]: https://twitter.com/mikeal/status/1000164993667555328

[JCSato]

*her/their tone, if you care

As the person mostly on the hook for https://news.ycombinator.com/item?id=16435305 (as I recall), I can imagine she/they would be a little on edge.

Still not a good look. . .

[pluma]

I see no reason why "they've screwed up before so it's okay if they're being dismissive and intransparent" would ever be a valid argument. The point of excusing past mistakes is that they are learning opportunities.

If anything, the filesystem permissions bug only makes this worse because it was a destructive bug in a widely promoted release (even if it was technically not supposed to be stable -- npm employees actively recommended using it on twitter) and npm's reaction was fairly dismissive (because it's not a stable release for production use, dummy).

[JCSato]

Only intended to explain, not excuse. I totally agree.