Welp, you can now watch me delivering the talk about why I think federated package management is what we should do. Ulp.https://youtu.be/MO8hZlgK5zc
-
-
Replying to @ceejbot
I remember that fall when npm would spontaneously fail all the time, and we even thought about putting up our own mirror/proxy couchdb. Now I know why. Also yarn uses their own registry, which make a lot of sense (FB/Google not being as threatened).
2 replies 0 retweets 0 likes -
Yarn's "registry" is a CNAME to npm, and Yarn isn't Facebook nor Google
2 replies 0 retweets 0 likes -
I did not know that, interesting. Makes me wonder why they bothered at all, but maybe that's an escape hatch for redirecting traffic if npm decides to go hard ball. Yarn is written by FB and Google, right?
1 reply 0 retweets 0 likes -
We’re pleased to announce the open source release of Yarn, a collaboration between Facebook, Exponent, Google, and Tilde. https://yarnpkg.com/blog/2016/10/11/introducing-yarn/ …
1 reply 0 retweets 0 likes -
While bootstrapped by those companies, Yarn is an independent community project, highlighted by it not being part of the facebook or github GitHub organizations (contrary to React or Jest, for example). Additionally, none of the active contributors work at Facebook at the moment.
1 reply 0 retweets 0 likes -
OK. The reason I see FB having control is that I saw this https://github.com/yarnpkg/rfcs/pull/101 … and it explicitly mentions FB running PnP in production. He's listed as a member of the org, which I think means he has commit rights.
2 replies 0 retweets 0 likes -
The reason I mention PnP is that it's a new* concept developed for use by FB and shared with the community. That, or they really wanted that feature and got it in b/c they're a founder. *I'm not sure if tink came first TBH
2 replies 0 retweets 0 likes
Sebastian Retweeted Sebastian
For what it's worth, we don't use PnP at Facebook anymore and won't be investing in ithttps://twitter.com/sebmck/status/1137059802838757377 …
Sebastian added,
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 