I hope they would do the right thing and move the registry to the Foundation.
-
-
Do we even know if that's an option? The founders may have been diluted, and the assets could be owned by the investors in the result of a closure. Will they be good stewards? Would they want to sell it off to earn back loss investment?
1 reply 0 retweets 2 likes -
If somebody buys npm, they would have all interests in keep the registry running. The Foundation is the natural destination. I would love to see the npm cli getting in there too (asap).
3 replies 0 retweets 11 likes -
Replying to @matteocollina @sebmck and
is there some urgency or news item I’m missing here
2 replies 0 retweets 4 likes -
Replying to @b0neskull @matteocollina and
I read that npm cut 10% of staff and did something relating to gag orders. Just from the info out there, it looks like a rough road forward, even from just a reputation POV.
1 reply 1 retweet 2 likes -
Replying to @jake_niemiec @matteocollina and
there’s nothing unusual about a severance package containing a non-disparagement clause
2 replies 0 retweets 4 likes -
Replying to @b0neskull @jake_niemiec and
additionally it's not hard to pull out double digit percentages when your staff is below 50 people
1 reply 0 retweets 7 likes -
Replying to @bitandbang @jake_niemiec and
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
2 replies 0 retweets 5 likes -
Replying to @b0neskull @bitandbang and
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.
2 replies 1 retweet 12 likes -
Replying to @sebmck @b0neskull and
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.
1 reply 0 retweets 0 likes
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.
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.
he/him 