News for hackers. Stuff that matters.

A comment on Yarn registry was down. Parent comment

Re:Yarn registry was down by mastahmind on Friday May 25, 2018 @08:39PM (#17159369)
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.
[ Parent | on HN ]
Re:Yarn registry was down by jessaustin on Friday May 25, 2018 @08:52PM (#17159422)
ISTM 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!
[ Parent | on HN ]
Re:Yarn registry was down by andrewshifflett on Saturday May 26, 2018 @02:49AM (#17160586)
CJ (CTO at npm) explained on Twitter why they switched to Cloudflare:

https://twitter.com/ceejbot/status/1000230136900239360

(See: https://developers.cloudflare.com/workers/about/)

[ Parent | on HN ]
Re:Yarn registry was down by asadlionpk on Saturday May 26, 2018 @02:30AM (#17160548)
Maybe future proofing? They can always make their own and just point CNAME to the new registry?
[ Parent | on HN ]