3 ms·

From section 1 of the tutorial: > Since it came out in October 2016, [Yarn] received a very quick adoption and is becoming the new package manager of choice of

From section 1 of the tutorial: > Since it came out in October 2016, [Yarn] received a very quick adoption and is becoming the new package manager of choice of the JavaScript community. We are going to use Yarn in this tutorial. It's October 2016 as I write. Tell me this tutorial is satire. Please.

joshkpeterson 10y ago
The thing is, Yarn is likely to supersede npm at the command line so this is really future-proof.
- kayamon 10y ago
  Until next month, when Flamphf replaces Yarn.
  - fnovd 10y ago
    Except Facebook is behind yarn. I'm about as worried about Flamphf replacing yarn as I am about Flamphf replacing React.
pault 10y ago
Welcome to front end development. :)
gotofritz 10y ago
Yarn solve some problems that the npm folks were unwilling / unable to solve, and is backed by Facebook + Google (+ others) so it's likely to be here to stay. Unless npm wake up and smell the coffee and implement some of it themselves, but experience shows they are quite opinionated and not in a good way.
- Klathmon 10y ago
  IIRC the yarn developers worked with NPM to get it out. It's not a lack of will or ability on the part of NPM that it can't be "fixed", it's that NPM has just so much baggage. They can't change how things are installed, because that would mean getting rid of features that many people rely on. For a while they didn't even have any documentation on how NPM worked, it was a bit tautological (npm worked in the way that npm worked...). And rather than add flags or settings to NPM to support yarn's use cases which would bloat the code, add a pretty sizable increase to maintenance and support, and would really be a mess, they decided to create their own tool which is similar enough to make it easy to switch, but without any of the legacy baggage that NPM needs to support. It's a perfect example of the unix philosophy at work ("Don't hesitate to throw away the clumsy parts and rebuild them."), and just about everyone (including NPM) is happy with the work they are doing.
  - oblio 10y ago
    I honestly don't know that part of the Unix philosophy. And it starkly contrasts with my experience related to Unix, where most of the time we throw nothing away.
  - gotofritz 10y ago
    There is no reason why npm couldn't have a lockfile, for example.
Kiro 10y ago
Step up your game.
skizm 10y ago
I think it is the worst/best kind of satire: The kind that is completely indistinguishable from how large groups of people actually operate.
morgante 10y ago
It's definitely an extreme position to take. A lot of people on HN seem to confuse the introduction of new tools with a necessity for you to constantly rewrite your app. There's nothing saying you need to adopt the new tools as soon as they come out. Personally, I like to give things a good while to work out the kinks and see if they're actually any good (Bower failed this test, for example, so I've never used it). In the meantime, my "old" tools still work fine. Despite all the talk of churn, the last time I actually added a new major tool to my stack was GraphQL this spring.
ng12 10y ago
Yarn is essentially a layer on top of NPM which was already the standard, hence the quick adoption. That aside god forbid anything get better quickly. Javascript developers should suffer like anyone else.

joshkpeterson 10y ago

The thing is, Yarn is likely to supersede npm at the command line so this is really future-proof.

kayamon 10y ago
Until next month, when Flamphf replaces Yarn.
- fnovd 10y ago
  Except Facebook is behind yarn. I'm about as worried about Flamphf replacing yarn as I am about Flamphf replacing React.

pault 10y ago

Welcome to front end development. :)

gotofritz 10y ago

Yarn solve some problems that the npm folks were unwilling / unable to solve, and is backed by Facebook + Google (+ others) so it's likely to be here to stay. Unless npm wake up and smell the coffee and implement some of it themselves, but experience shows they are quite opinionated and not in a good way.

Klathmon 10y ago
IIRC the yarn developers worked with NPM to get it out. It's not a lack of will or ability on the part of NPM that it can't be "fixed", it's that NPM has just so much baggage. They can't change how things are installed, because that would mean getting rid of features that many people rely on. For a while they didn't even have any documentation on how NPM worked, it was a bit tautological (npm worked in the way that npm worked...). And rather than add flags or settings to NPM to support yarn's use cases which would bloat the code, add a pretty sizable increase to maintenance and support, and would really be a mess, they decided to create their own tool which is similar enough to make it easy to switch, but without any of the legacy baggage that NPM needs to support. It's a perfect example of the unix philosophy at work ("Don't hesitate to throw away the clumsy parts and rebuild them."), and just about everyone (including NPM) is happy with the work they are doing.
- oblio 10y ago
  I honestly don't know that part of the Unix philosophy. And it starkly contrasts with my experience related to Unix, where most of the time we throw nothing away.
- gotofritz 10y ago
  There is no reason why npm couldn't have a lockfile, for example.

Kiro 10y ago

Step up your game.

skizm 10y ago

I think it is the worst/best kind of satire: The kind that is completely indistinguishable from how large groups of people actually operate.

morgante 10y ago

It's definitely an extreme position to take. A lot of people on HN seem to confuse the introduction of new tools with a necessity for you to constantly rewrite your app. There's nothing saying you need to adopt the new tools as soon as they come out. Personally, I like to give things a good while to work out the kinks and see if they're actually any good (Bower failed this test, for example, so I've never used it). In the meantime, my "old" tools still work fine. Despite all the talk of churn, the last time I actually added a new major tool to my stack was GraphQL this spring.

ng12 10y ago

Yarn is essentially a layer on top of NPM which was already the standard, hence the quick adoption. That aside god forbid anything get better quickly. Javascript developers should suffer like anyone else.