4 ms·
I was under the impression that this was about speed. There are many use cases for this functionality, the design of a software package shouldn't instill dogma
by akhatri_aus 10y ago
I was under the impression that this was about speed.
There are many use cases for this functionality, the design of a software package shouldn't instill dogma into its users. Users use software for their needs, not to sign up to a religion.
- skrebbel 10y agoNo, speed is bonus. Yarn is about reproducible dev/test/build setups. Same yarn.lock - same node_modules content. That's the primary goal. If you think consistency across computers is a religion then I don't think we're going to find a lot of common ground here though. Finally, yarn is not intended to replace the npm client. It is intended to replace it for a certain use case, which happens to be one many companies have. Unlike Yarn, Npm is highly flexible and obviously you like it like that. I strongly doubt it's going to stop being developed all of a sudden because some other people made Yarn. So what, exactly, is the problem?
- akhatri_aus 10y ago> So what, exactly, is the problem? Follow users needs, not your idea of what they are or the problems with npm are.