4 ms·
I agree with the comments in this thread, and I add that Facebook knows fanboys are stupid and there are a lot of them, so they try to take advantage of it. >
by fibo 10y ago
I agree with the comments in this thread, and I add that Facebook knows fanboys are stupid and there are a lot of them, so they try to take advantage of it.
> Buck: A high-performance build tool
And in the title you read "a fast build tool", like yarn, as soon as it was released it was the faster one.
F: let's use yarn/buck
G: why?
F: cause it is faster
G: Did you already tryed it? Did you measured or benchmarked it?
F: No, but Facebook claims it is fast, come on!
By the way, sometimes yarn does not work and you need to add a file to manage it. Furthermore facebook is using the npm registry, do they pay for it or support it?
Other than that, thanks to Facebook to bring awesome tools to the public, like React.
- noir_lord 10y agoFor my needs yarn was a drop in replacement for npm and it is faster, 5s vs 17s for a fresh install but critically it's reproducible, I get the exact same output in node_modules every time I run it and that alone was worth the switch. As for using the npm registry (by default) so what? Why would the npm folks care, MS uses it as well with vscode ans its automatic resolution.
- jcheng 10y agoAgreed that yarn is faster and reproducibility is critical, but in case you aren't aware, you can have reproducibility with npm too by using the "npm shrinkwrap" command.
- TheCoelacanth 10y agoUpdating a single package version in a yarn.lock file is much easier than updating a single package version in an npm shrinkwrap file, in my experience. With yarn it's just a single command. With npm shrinkwrap, you have install everything from the current snapshot, then install the package you want to update, then run npm prune, then regenerate the shrinkwrap file, then look through hundreds of lines of mostly irrelevant diff to make sure that it did what you wanted it to.