4 ms·
well, you can look at it at both ways, if yarn just used npm's registry then there wouldn't be a problem. I am not sure what's their reason to add a registry (a
by mastahmind 8y ago
well, you can look at it at both ways, if yarn just used npm's registry then there wouldn't be a problem. I am not sure what's their reason to add a registry (a mirror at that) if they don't plan to make their own.
- jessaustin 8y agoISTM this was a marketing ploy for yarn. If CF could proxy npm's registry faster than npm could serve it directly, yarn could claim to be faster than npm. Even if the apps themselves had been identical, network speed is still speed. As we could expect for any competitive advantage that is purchased by one party, it has now been purchased by another party, so it ceases to be an advantage at all. The Red Queen lives!
- andrewshifflett 8y agoCJ (CTO at npm) explained on Twitter why they switched to Cloudflare: https://twitter.com/ceejbot/status/1000230136900239360 https://twitter.com/ceejbot/status/1000230136900239360 (See: https://developers.cloudflare.com/workers/about/ https://developers.cloudflare.com/workers/about/)
- asadlionpk 8y agoMaybe future proofing? They can always make their own and just point CNAME to the new registry?