SebastianVerified account

Update: It's pretty disheartening to learn that the Yarn team decided to simply refuse to make these changes, which would have no measurable performance or operational impact. It's been a big challenge to get them to cooperate with us on anything even with extended olive brancheshttps://twitter.com/maybekatz/status/953765220819742720 …

My team's taken the initiative on a number of occasions to give them early information about changes, to share code and libraries, to show up on their issue tracker and provide as much detail about our inner workings as we can when they're implementing their own features.

but the feeling on my end is that this exchange has been universally one-sided: as far as I know, Yarn does not share a single line of code or npm-maintained dependency with npm. They've taken -my- patches but have never offered or considered submitting their own, even once.

I guess this follows the precedent set by writing a complete thing from scratch without ever offering to help a small company's open source project. Hooray for Corporate Open Source™ I guess.

And to drive the grumble home: "sustainable community" does not mean "let's get free labor to write all our features for this tool that's primarily for our own benefit and put as little effort into it as we can" It's *promoting a healthy community and ecosystem*

I'm angry and kinda grossed out by Facebook's approach to open source now. I hope they stop being this way. The Yarn devs have been really nice and friendly whenever we've had 1:1 convos but I suspect there's major organizational pushback against being good neighbors.