he/him 
Here's an interesting question, what would the fallout be if npm, inc just straight up went mental and blocked the registry? Would companies such as Microsoft who have deeper legal pockets have a case against them for disruption, or what would happen?
-
granted, a foundation-managed registry might be good, and contingency plans are good. but how we got from layoffs to “impending doom” seems like classic alarmist twitter
I think you'll find that everyone in this thread has been thinking about this for a loooong time. The new CEO, layoffs, and questionable behaviour from the company have just exposed these concerns to more people.
-
-
I actually never knew about this stuff until your thread. Hadn't paid attention. But I've had similar discussions about this with other node devs for at least 2-3 years that I can remember.
-
I've been thinking about it for over 3 years while I was building
@yarnpkg. Not trusting npm inc is literally the reasonthat Yarn uses http://registry.yarnpkg.com by default. Trivial to point it somewhere else.
End of conversation
New conversation -
-
-
I’m gonna go out on a limb and suggest that some communication from the top @
@npmjs to the effect of “don’t worry, everything is fine” might calm some nerves. -
Any central point of failure is a concern, even without any additional points. Whenever these things happen it just re-ignites peoples existing concerns with that central problem. This is probably why people are so upset about anything to do with Facebook, nowhere else to go.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.