I hereby claim:
- I am jasnell on github.
- I am jasnell (https://keybase.io/jasnell) on keybase.
- I have a public key whose fingerprint is 71DC FD28 4A79 C3B3 8668 286B C97E C7A0 7EDE 3FC1
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
| const { createHook } = require('async_hooks'); | |
| const { promisify } = require('util'); | |
| const sleep = promisify(setTimeout); | |
| let count = 0; | |
| const hook = createHook({ | |
| init(id, type) { | |
| if (type === 'PROMISE') | |
| count++; |
| * it was a mistake to let npm, inc. get as far as it did with what should have always been a part of the foundation (post Joyent). | |
| * The CLI isn't the interesting part – the registry contains the value & needs to be safeguarded. | |
| * I really strongly dislike Facebook and don't trust anyone that takes a paycheck or benefits at all from that brand. NPM is know to not be well managed but I really don't like Facebook. | |
| * "Dear God please don't ship Yarn by default. Not only are the maintainers unpleasant to interact with, the whole thing is just... bad. | |
| * Most of the time fixing Yarn issues comes down to: ""Can you try npm instead?"". Making that a default experience would be a catastrophy." | |
| * I am more concerned about the stability of the npm package management repo than necessarily npm vs yarn. | |
| * I remember when node didn't come with a package manager, it was pretty bad | |
| * the problem is not the package manager, it’s the registry. Currently the registry is not owned the foundation. no matter what the client is, we |