SebastianVerified account

(it's also able to guarantee you get the same tree between two different installs. yarn's guarantees around this are notably weaker)

you can see it as a tradeoff: npm might usually be slightly slower, but it does a lot more work. yarn prioritizes speed over reliability.

> yarn prioritizes speed over reliability This isn't really true. Yarn was originally started to ensure deterministic installs.

It has been and continues to be the main focus.

Yet Yarn trusts way more of its system, for the sake of performance. Cache corruption is undetectable. :\

Only direct user modification of the cache can cause corruption. Yarn's cache is atomic. .yarn-metadata.json is verified for existence...

and is only written after a verified cache write.

we literally have folks in the wild who have complained about `~/.npm` being corrupted by many other factors external to npm besides user.