u/ecaresin r/node • Recommends
The economics of open source by C J Silverio | JSConf EU 2019
0:00 / 0:00
The economics of open source by C J Silverio | JSConf EU 2019
JSConf
286K subscribers • 28 videos on Hallway
- Recommended by 4 people: 2 on Hacker News, 1 on Lobsters and 1 in engineering communities.
- Presented by C J Silverio, former npm CTO
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
92K views7 years ago4 recommendations
Tools and practiceCareers and interviewsOpen sourceThe tech industryNode.js, Deno and Bun
Former npm CTO C J Silverio discusses the challenges of a centralized, for-profit entity controlling the JavaScript package registry and proposes decentralized alternatives.
The JS package commons is in the hands of a for-profit entity. We trust npm with our shared code, but we have no way to hold npm accountable for its behavior. A trust-based system cannot function without accountability, but somebody still has to pay for the servers. How did we get here, and what should JavaScript do now? 2019.jsconf.eu/c-j-silverio/the-economics-of-open-source.htm…Why it's here
4 people recommend thisWhat people say. Highly recommended for its insightful critique of npm's centralized model and the economic realities of maintaining open-source package registries.
unbalancedparentheseson Lobsters • Recommends
The economics of open source
The talk is given by C J Silverio, ex CTO of npm, Inc.
pier25on Hacker News • Recommends
On “Pika CDN – A CDN for Modern JavaScript”
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: link to this video
drejon Hacker News • Recommends
On “Pika – A JavaScript package registry for the modern web”
For those wondering what's wrong with npm, I can recommend this C J Silverio talk link to this video Sadly, as others have noted, this Pika thing does not quite address these issues.
kostareloon Hacker News • Mentions
On “Entropic – A Federated Package Manager for JavaScript”
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: link to this video
TimothyBJacobson Hacker News • Mentions
On “NPM CEO Bryan Bogensberger Resigned”
There has been. CJ Silverio gave a talk on that topic at JSConf this year: link to this video See also Entropic as a possible alternative to NPM: link
drewbug01on Hacker News • Mentions
On “GitHub has completed its acquisition of NPM”
> 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 NPM). I mean, the difference between them is slight; and there's overlap. They both resolve package dependencies and sort out problems, for example. But they're such very, very different things! It's not really fair to compare these two approaches and say things about Composer like "this allows them…