4 ms·

"Github acquires npm" would be a better title IMO.

by sandov 7y ago

kdaigle 7y ago
Today we've announced that we've signed an agreement to acquire NPM but we technically have not acquired them yet (referred to as "closed"). NPM is still their own company for now and that's why the language is future tense.
- sandov 7y ago
  "Github is acquiring npm" then. "NPM is joining Github" sounds like you're just using Github to host your stuff.
  - Conan_Kudo 7y ago
    Using the "is joining" phrasing is a classic way to try to spin an acquisition as some kind of partnership. 99% of the time, it's definitely not.
  - rdiddly 7y ago
    I literally thought that, clicked hide, then thought "Wait a minute, do they mean...?" and had to go fish it out of hidden items. "Joining" is an interesting term here... but I suppose it won because it sounds more like something friendly humans would do. "NPM Is Breaking Bread and Sharing with Github as Special Friends."
- TheKarateKid 7y ago
  Then saying "GitHub is acquiring NPM" would've been a more accurate way to say this.
hinkley 7y ago
I am glad that the npm team will finally have some adult supervision. Meanwhile, I almost have my team switched to yarn.
- Normal_gaussian 7y ago
  yarn v1+ or yarn v2/berry? Switching to berry has been a huge PITA over here, but I don't want to give up workspaces
  - hinkley 7y ago
    Our 'workspace' is so ornate that yarn couldn't handle it. 1.21+ almost looks right, but something very bad is still going on with mocha deduping, such that tests are failing with really bizarre error messages. I check yarn about every three months, or when I find a new, infuriating bug with the npm CLI (so, every couple of months on average). I think npm install suffers greatly from not having a formal spec. It has been bugfixed by so many different individuals now that it has reached a truly astounding level of schizophrenia. If yarn didn't exist, I would have started trying to break down the install problem into many independent concerns that can be reasoned about individually and tried to solicit help in making a full installer out of it. If I'd known I'd still be trying to make yarn workspaces work for us 18 months later I probably would have. Node modules in general have some bad patterns of delegation that are utterly antagonistic to self-documentation, and both yarn and npm seem to suffer from this as well. I think in the next week or so I'm going to have to set up a small test case that exhibits the yarn bug I'm seeing, or any of the half a dozen interlocking (emphasis on 'lock') npm bugs that now have me painted into a very tiny corner.
    - IsaacSchlueter 7y ago
      Your take on the installer in npm v6 is not wrong. It got that way by a process of gradual iterative evolution, and it has lots of warts. npm v7 features a ground-up rewrite of the tree resolution and deification logic in the @npmcli/arborist module. I recommend checking it out, or at least staying tuned for the beta coming soon.
  - hinkley 7y ago
    > yarn v2/berry? I had still been following 1.x Looking at https://yarnpkg.com/advanced/migration https://yarnpkg.com/advanced/migration : T-T We have so many little modules from different teams, or even borderline abandonware, that it would take ages to make these changes, and 'yarn node'?? Just... no. How is that ever gonna work consistently with node_modules/.bin? At this point my choices are, start contributing to yarn and npm development, or get my ass in gear on learning Elixir and Rust. I have been wondering for maybe 18 months if I might be 'done with Node'. I think I've had it backward this whole time. Node may in fact be done with me.
ProAm 7y ago
"Microsoft acquires npm"
Verdex 7y ago
Yeah, I was confused when I first heard of it because it seems like an odd couple to "join" one another. However, it makes perfect sense for github to purchase npm.

"Github acquires npm" would be a better title IMO.

by sandov 7y ago

"Github acquires npm" would be a better title IMO.

Today we've announced that we've signed an agreement to acquire NPM but we technically have not acquired them yet (referred to as "closed"). NPM is still their own company for now and that's why the language is future tense.

sandov 7y ago
"Github is acquiring npm" then. "NPM is joining Github" sounds like you're just using Github to host your stuff.
- Conan_Kudo 7y ago
  Using the "is joining" phrasing is a classic way to try to spin an acquisition as some kind of partnership. 99% of the time, it's definitely not.
- rdiddly 7y ago
  I literally thought that, clicked hide, then thought "Wait a minute, do they mean...?" and had to go fish it out of hidden items. "Joining" is an interesting term here... but I suppose it won because it sounds more like something friendly humans would do. "NPM Is Breaking Bread and Sharing with Github as Special Friends."
TheKarateKid 7y ago
Then saying "GitHub is acquiring NPM" would've been a more accurate way to say this.

hinkley 7y ago

I am glad that the npm team will finally have some adult supervision. Meanwhile, I almost have my team switched to yarn.

Normal_gaussian 7y ago
yarn v1+ or yarn v2/berry? Switching to berry has been a huge PITA over here, but I don't want to give up workspaces
- hinkley 7y ago
  Our 'workspace' is so ornate that yarn couldn't handle it. 1.21+ almost looks right, but something very bad is still going on with mocha deduping, such that tests are failing with really bizarre error messages. I check yarn about every three months, or when I find a new, infuriating bug with the npm CLI (so, every couple of months on average). I think npm install suffers greatly from not having a formal spec. It has been bugfixed by so many different individuals now that it has reached a truly astounding level of schizophrenia. If yarn didn't exist, I would have started trying to break down the install problem into many independent concerns that can be reasoned about individually and tried to solicit help in making a full installer out of it. If I'd known I'd still be trying to make yarn workspaces work for us 18 months later I probably would have. Node modules in general have some bad patterns of delegation that are utterly antagonistic to self-documentation, and both yarn and npm seem to suffer from this as well. I think in the next week or so I'm going to have to set up a small test case that exhibits the yarn bug I'm seeing, or any of the half a dozen interlocking (emphasis on 'lock') npm bugs that now have me painted into a very tiny corner.
  - IsaacSchlueter 7y ago
    Your take on the installer in npm v6 is not wrong. It got that way by a process of gradual iterative evolution, and it has lots of warts. npm v7 features a ground-up rewrite of the tree resolution and deification logic in the @npmcli/arborist module. I recommend checking it out, or at least staying tuned for the beta coming soon.
- hinkley 7y ago
  > yarn v2/berry? I had still been following 1.x Looking at https://yarnpkg.com/advanced/migration https://yarnpkg.com/advanced/migration : T-T We have so many little modules from different teams, or even borderline abandonware, that it would take ages to make these changes, and 'yarn node'?? Just... no. How is that ever gonna work consistently with node_modules/.bin? At this point my choices are, start contributing to yarn and npm development, or get my ass in gear on learning Elixir and Rust. I have been wondering for maybe 18 months if I might be 'done with Node'. I think I've had it backward this whole time. Node may in fact be done with me.

ProAm 7y ago

"Microsoft acquires npm"

Verdex 7y ago

Yeah, I was confused when I first heard of it because it seems like an odd couple to "join" one another. However, it makes perfect sense for github to purchase npm.