3 ms·
The circular dependency problem is kind of "90's interview question" easy (source: I was asked this in an interview in the 90's). What other comically obvious
by chaboud 3y ago
The circular dependency problem is kind of "90's interview question" easy (source: I was asked this in an interview in the 90's). What other comically obvious lessons remain to be painfully learned for npm folks?
- internetter 3y agoWe'll see if there is any real policy change. I hope there is, at the very least to avoid another instance of this mistake, but also to prevent genuine targeted abuse of this policy failure. For now, NPM is slowly taking all the packages down, and GitHub has forcefully made the org private: https://imgur.com/a/WuSpBQi https://imgur.com/a/WuSpBQi
- RamblingCTO 3y agoThe worst thing is that this already happened in January 2023. NPM again showing that only the brightest of the brightest are working on this ecosystem o7
- internetter 3y agoAs far as we know, NPM's solution was to flag the organization (making the links to the issues within the article useless) and to remove the packages without any policy change.
- exabrial 3y agoBecause node is a comedy. It’s intentionally making a very easy problem into a Rube Goldberg machine.
- intunderflow 3y agoThey won't learn anything from this, they'll blame the authors for "using NPM wrong" just like the dogpiling comments were on the everything repo before mass flagging by the same people booted it off GitHub.