111–120 of 588 posts
Oops. So NPM will go down, soon. I just finished reading this related HN post "How GitHub blocked me (and all my libraries)" https://news.ycombinator.com/item?id=22593595
There's a difference between NPM the client and NPM the registry. You can point the client to any registry you want - there are a ton of options.
Earlier quoted context omitted.
I installed Windows Subsystem for Linux 2 on an older machine just now. The MSFT of today is definitely a far cry from the MSFT of yesteryear. Such a thing would have been unheard of 15 years ago.
Embrace, extend, extinguish?
WSL1 was a proprietary reimplementation of the Linux system call ABI as an NT subsystem. WSL2 is actual Linux running in a VM. That seems to be moving in exactly the opposite direction.
Earlier quoted context omitted.
It was already consolidated. The vast majority of public npm packages are already hosted on Github. The dependency on them has been there since the beginning.
Yes, indeed - and the dependency is literally right there on the technical level. For years, you've been able to specify a version of a package as a github repo's branch HEAD. npm i some-package username/repo#branchName
https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extingu... Whelp, time to look for backup solutions for when Microsoft continues their strategy. Even today there’s an article about github flagging (re shadow banning) a user with 10k+ lib users, and no response from them as to why the ban occurred. Thinking of adding an “in case of emergency” link in my README for users in case of sudden service loss.
I wonder why your (entirely reasonable) comment got down-voted so much. This is exactly the risk why people prefer a distributed and decentralized internet over one where all open source is stored in one central Microsoft subsidiary (e.g. GitHub).
Anyone can already run their own, or install from remote git urls (not just github) as well. If the new organization undermines the community, the community can easily move.
NPM the company has had a significant number of missteps, and them getting better oversight and removing the need to be profitable will likely be better for everyone in the long run.
Earlier quoted context omitted.
Am I weird for thinking it didn't need to go anywhere?
My understanding was that financially they were not going to last long doing what they were doing.
Most people don’t know, in these open source acquisitions by for profits there’s money involved and “founders” get an exit. Not always clear To the public who those are or what they took home from a mostly volunteer effort.
Earlier quoted context omitted.
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.
"Github is acquiring npm" then. "NPM is joining Github" sounds like you're just using Github to host your stuff.
Heh, I called this 10 months ago: https://news.ycombinator.com/item?id=19838122 Somebody replied "Microsoft won't acquire npm for sure."
Earlier quoted context omitted.
I installed Windows Subsystem for Linux 2 on an older machine just now. The MSFT of today is definitely a far cry from the MSFT of yesteryear. Such a thing would have been unheard of 15 years ago.
Embrace, extend, extinguish?
I'm surprised there's not a single mention of "Microsoft" in this or the npm announcement [1], given the old-evil-history of Microsoft and the new-nice Microsoft we have today. I would expect that there was at least a mention, considering the reason that most modules in npm are still in ES5 is exactly because of the monopolistic practices that Microsoft followed back in the day which makes Internet Explorer still rel…
I installed Windows Subsystem for Linux 2 on an older machine just now. The MSFT of today is definitely a far cry from the MSFT of yesteryear. Such a thing would have been unheard of 15 years ago.