The economics of open source by C J Silverio | JSConf EU 2019

Channel:JSConf · Length:37:43 · Published:2019-06-03 · Views:92491

Watch on YouTube

Summary

C J Silverio, former npm CTO, explains how the JavaScript package commons ended up in the hands of a for-profit company with no accountability. She discusses the cost of running a registry and what the community should do next.

Why HN recommends it

HN recommends it as the best account of what is wrong with npm's governance and why alternative or decentralized registries are hard.

For those wondering what's wrong with npm, I can recommend this C J Silverio talk — HN, 2019

Web development · Software practice, open source & careers

Subtitles (excerpt)

>> All right! You're tired? You're hot, it's been a long day. Shake it out a little bit. Shake it out. All right. Here we are. So, I'm going to talk about economics of package management, and more specifically in open source. It's - I'm going to tell you a story about who owns the JavaScript language commons, how we got into this situation with the JavaScript language commons is by someone, and why we need to change it. This is a story about money, ownership, and control, as much as it is about JavaScript. I am going to tell you this story. I'm going to tell you the version of the story I know how to tell. I'm one human being with imperfect knowledge as a point of view, so this story is not the only story anyone could tell about it - not by a long way. I could tell you a good version of one slice of this story because I was part of it. I was at its heart, because, until last year, I was CTO of NPM Inc. This gives me an expertise on the topic few people in the world have. It also comes with a point of view, and I'm going to invite you to keep my point of view in mind as you hear this story. You're in this story. Yes, you. I bet you didn't know you were part of this story. You will know why you're part of it, and you

On Hacker News

For those wondering what's wrong with npm, I can recommend this C J Silverio talk [VIDEO] Sadly, as others have noted, this Pika thing does not quite address these issues. — drej, 2019-11
This is a great recent talk about this problem by the former NPM CTO in which she tells her story about NPM and proposes a new decentralized package manager: [VIDEO] — pier25, 2019-06
> This massively depends on the architecture of the package manager though. Composer (PHPs primary package manager) only serves the metadata See also, CocoaPods. But we're really talking about two things here as if they're the same, and I think it's because the language we use for them isn't clear: package managers (like CocoaPods and Composer) and full-blown package registries (like RubyGems and… — drewbug01, 2020-04
There has been. CJ Silverio gave a talk on that topic at JSConf this year: [VIDEO] See also Entropic as a possible alternative to NPM: [LINK] — TimothyBJacobs, 2019-09
I am trying to understand why we make NPM such a big deal (and suddenly have all these projects born to solve the NPM problem) when people have solve the issue of a package repository already. C j Silverio's point (JSConf's talk [1]) was that is NPM's scale that makes it hard. Refs: 1: [VIDEO] — kostarelo, 2019-06

Related videos