5 ms·

Why would it be a bad thing to support additional repositories? Personally, I don't like how centralized the JS ecosystem is. For example, if I refer to 'left-

by evv 10y ago

Why would it be a bad thing to support additional repositories? Personally, I don't like how centralized the JS ecosystem is. For example, if I refer to 'left-pad', it would default to 'npmjs.org/left-pad'. If the author goes rougue, I think it would be great to enable people to publish and consume 'thirdparty.com/left-pad' Disclosure: I'm a FB employee with no knowledge of our plans in this regard

swang 10y ago
1. any left-pad issue has been "eliminated" with the new rules npm (the company) has enforced. 2. you can already have your own version of thirdparty/left-pad by maintaining your own npm repository. i think what your parent post is referring to is facebook saying we're going to make our own public node/javascript package registry and you should publish to our registry. doing this at the moment does nothing for the community other causing a lot of pain points. ex) now npm authors will have to publish to both registries so developers don't have to dig to find where it was published to, then they also have to hope that someone else didn't register the module name in one of the registries.. there is just too much splintering if facebook decided to become a competing registry rather than just using npm's registry and building on top of it.
- dmitriid 10y ago
  > any left-pad issue has been "eliminated" with the new rules npm (the company) has enforced. Only to resurface again: http://status.npmjs.org/incidents/dw8cr1lwxkcr http://status.npmjs.org/incidents/dw8cr1lwxkcr And it will, no doubt, resurface again and again and again
joepie91_ 10y ago
Have a read here: https://github.com/nodejs/NG/issues/29#issuecomment-174314526 https://github.com/nodejs/NG/issues/29#issuecomment-17431452... - it's a writeup that I made a while ago about the requirements for a stable (decentralized) package registry, and it addresses your question as well.
davidascher 10y ago
Somewhat funny to have an FB employee complaining about overly centralized systems.
- foo101 10y ago
  I used to find such comments funny until I began working for Big Name Corps myself and I realized how much one's personal philosophy could be inconsistent or sometimes even contradictory to the employer's philosophy. I make money by selling my skills to an employer despite inconsistent philosophies. I think it's like a chef that can cook meat for his/her guests although the chef has decided to refrain from consuming meat himself/herself.
  - suls 10y ago
    It's sort of related to the principal-agent problem ..
  - davidascher 10y ago
    Yup. And such a chef probably wouldn't publicly berate people for eating meat, or expect being called out if they did.
    - foo101 10y ago
      Yup. And I don't see anyone berating anybody in this thread. Do you?
  - davidascher 10y ago
    Yup. And such a chef probably wouldn't publicly berate people for eating meat, or expect being called out if they did.

by evv 10y ago

swang 10y ago

1. any left-pad issue has been "eliminated" with the new rules npm (the company) has enforced. 2. you can already have your own version of thirdparty/left-pad by maintaining your own npm repository. i think what your parent post is referring to is facebook saying we're going to make our own public node/javascript package registry and you should publish to our registry. doing this at the moment does nothing for the community other causing a lot of pain points. ex) now npm authors will have to publish to both registries so developers don't have to dig to find where it was published to, then they also have to hope that someone else didn't register the module name in one of the registries.. there is just too much splintering if facebook decided to become a competing registry rather than just using npm's registry and building on top of it.

dmitriid 10y ago
> any left-pad issue has been "eliminated" with the new rules npm (the company) has enforced. Only to resurface again: http://status.npmjs.org/incidents/dw8cr1lwxkcr http://status.npmjs.org/incidents/dw8cr1lwxkcr And it will, no doubt, resurface again and again and again

joepie91_ 10y ago

Have a read here: https://github.com/nodejs/NG/issues/29#issuecomment-174314526 https://github.com/nodejs/NG/issues/29#issuecomment-17431452... - it's a writeup that I made a while ago about the requirements for a stable (decentralized) package registry, and it addresses your question as well.

davidascher 10y ago

Somewhat funny to have an FB employee complaining about overly centralized systems.

foo101 10y ago
I used to find such comments funny until I began working for Big Name Corps myself and I realized how much one's personal philosophy could be inconsistent or sometimes even contradictory to the employer's philosophy. I make money by selling my skills to an employer despite inconsistent philosophies. I think it's like a chef that can cook meat for his/her guests although the chef has decided to refrain from consuming meat himself/herself.
- suls 10y ago
  It's sort of related to the principal-agent problem ..
- davidascher 10y ago
  Yup. And such a chef probably wouldn't publicly berate people for eating meat, or expect being called out if they did.
  - foo101 10y ago
    Yup. And I don't see anyone berating anybody in this thread. Do you?
- davidascher 10y ago
  Yup. And such a chef probably wouldn't publicly berate people for eating meat, or expect being called out if they did.