RIP NPM
NPM Is Joining GitHub
91–100 of 588 posts
Re: NPM Is Joining GitHub
#92https://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).
I think people are tired of EEE being posted on every Microsoft related thread even though Microsoft has been a very different company for at least 10 years.
I do agree with the concerns of open source consolidation though. We need to find better ways of supporting open source projects instead of having them being bought by "large company".
Re: NPM Is Joining GitHub
#93NPM is joining GitHub, GitHub joins Microsoft, Microsoft joins... ;)
Re: NPM Is Joining GitHub
#94This seems like a good outcome overall. NPM being such an important pillar in the software supply chain while having an unviable business model and largely being funded by VC money was never a good position to be in. There are problems with more of the software ecosystem consolidating with a single entity but it still feels like an improvement.
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
Re: NPM Is Joining GitHub
#95Thanks to Microsoft/GitHub for this acquisition. NPM is essential to the Javascript eco-system and it is hard to have a business model for just a registry. In the ruby eco-system the awesome Ruby Together https://rubytogether.org/ was started to run the registry. In this case one of the worlds most valuable companies will run it, which means it doesn't need a not-for-profit. Regarding "trace a change from a GitHub pu…
Just to clarify, RubyCentral http://rubycentral.org is running the RubyGems registry.
It's confusing. RubyCentral pays for hosting and "ops" (not sure how much 'ops' staff time, if any?), but I think not development? And RubyTogether hypothetically pays for development (some but not neccesarily all that's needed), which can include new features but also required maintenance (we all know software requires care and feeding, it's never "done")?
But I could have this not right?
It has been confusing for a variety of reasons.
And I think there are mixed reviews with how well it's going overall, especially the RubyTogether part.
Re: NPM Is Joining GitHub
#96VsCode, Typescript, Github, NPM. And Microsoft doesn't even have to maintain the main runtime, Google does. What a clever strategy!
Yes, they almost own the entire JS ecosystem at this point.
They lost a decade of battles for the web, but it seems they just found a way to get back in the fight.
Now at the IE 6 times, that meant monopoly, and it was terrible news.
But today, it means more competition between the giants, which is very good for us.
Re: NPM Is Joining GitHub
#97You know, my initial reaction was... oh no, the toxic people who run NPM and Node.js[1][2] are going to infect GitHub. But then I read that other front page article about the guy that got mysteriously "flagged", and the invasive questions he was asked. Maybe Github is already too far gone. Maybe it should be... please, bundle all the toxic people together in one spot, and let it all come crashing to the ground. I've…
Wishing ill on others or their projects ("it'd be great if they ceased to exist") does not reduce toxicity.
Re: NPM Is Joining GitHub
#98I'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…
My fear might probably be unfounded, but NPM is an integral part of the JS ecosystem. And given MicroSoft has .NET Core, I have a strange feeling that they'll concentrate on npm less.
I think they view it as way to make Core more reliable. Core relies community developed - npm hosted - tools like gulp and webpack. Unlike the full Framework, Core doesn't have "built-in" or "endorsed" bundling solution.
Re: NPM Is Joining GitHub
#99This seems like a good outcome overall. NPM being such an important pillar in the software supply chain while having an unviable business model and largely being funded by VC money was never a good position to be in. There are problems with more of the software ecosystem consolidating with a single entity but it still feels like an improvement.
Exactly, especially given the instability over at NPM. Hopefully MS / Github can be a stabilizing influence both financially and culturally.
Re: NPM Is Joining GitHub
#100Time to get behind Deno
https://en.m.wikipedia.org/wiki/Deno_(software)
Built by the node team to replace node.