Read on TwitterPlease give it just a minute before you assume I& #39;m talking about repeating all the mistakes of other package distribution systems
To people who say this would be like Go or bower or deno: No. That& #39;s not what I& #39;m talking about.
Those systems all rely on individuals to maintain their own repos. I& #39;m talking about repos that are managed solely by the registry. Immutability is guaranteed. GH is just the db.
Those systems all rely on individuals to maintain their own repos. I& #39;m talking about repos that are managed solely by the registry. Immutability is guaranteed. GH is just the db.
To those who think it would be slow: No.
You would obviously still need an actual registry server that resolves semver. GH wouldn& #39;t handle that for you. So you put the registry behind a cache/CDN, same as npm currently does. It would be just as fast.
You would obviously still need an actual registry server that resolves semver. GH wouldn& #39;t handle that for you. So you put the registry behind a cache/CDN, same as npm currently does. It would be just as fast.
Anyway, maybe I just did a poor job of explaining it.
When I first told people about unpkg they thought it was a dumb. But now we serve billions of requests every day.
https://abs.twimg.com/emoji/v2/... draggable="false" alt="🤷♂️" title="Achselzuckender Mann" aria-label="Emoji: Achselzuckender Mann">
I should probably just build it and stop talking about it... then you& #39;ll get ithttps://abs.twimg.com/emoji/v2/... draggable="false" alt="😅" title="Lächelndes Gesicht mit offenem Mund und Angstschweiß" aria-label="Emoji: Lächelndes Gesicht mit offenem Mund und Angstschweiß">
When I first told people about unpkg they thought it was a dumb. But now we serve billions of requests every day.
I should probably just build it and stop talking about it... then you& #39;ll get it
