5 ms·
Thanks 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 t
by sytse 7y ago
Thanks 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/ 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 pull request to the npm package version that fixed it" will there be an API to add a source in case the change was made outside of GitHub? Although I recognize that the vast majority of changes to npm packages happen on GitHub.
- tenderlove 7y agoJust to clarify, RubyCentral http://rubycentral.org http://rubycentral.org is running the RubyGems registry.
- jrochkind1 7y agoIt'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.
- sytse 7y agoThanks for that clarification, I was not aware of that. Thanks RubyCentral!
- Vinnl 7y agoThat must make you nervous over at GitLab, no? GitLab's integrated workflow is one of its main selling points (I love it), and GitHub now seems to be well underway to cross that moat.
- mavsman 7y agoReminds me of what happened with Cloud9 and VS Code. First, Cloud9 was awesome for allowing devs to code remotely. Then once VS Code became the best editor out there, they added remote host support (among other things) and now Cloud9 caters to a different audience entirely.
- sytse 7y agoIt is exciting to see that having everything in a single application is being validated by GitHub. Last year it was very clear they are switching from a marketplace model to a single application by including Verify (CI), Package, and Secure. We think Git(Lab|Hub) will become the two most popular solutions and we look forward to this competition https://about.gitlab.com/handbook/leadership/biggest-risks/#competition https://about.gitlab.com/handbook/leadership/biggest-risks/#... I think the companies that should be nervous are ones that have only one stage or ones that have multiple stages but as a suite of applications instead of a single application https://about.gitlab.com/handbook/product/single-application/ https://about.gitlab.com/handbook/product/single-application... There are a lot of these https://about.gitlab.com/devops-tools/ https://about.gitlab.com/devops-tools/
- IAmEveryone 7y ago> It is exciting to see that having everything in a single application is being validated by GitHub I wish Gitlab would get over this passive-aggressive negging of GitHub. I would squirm seeing something like that among any two competing companies. But it takes a strange configuration of overcompensating an inferiority complex to use it for the specific case of one company starting out as an explicit clone of another, to then lord any small feature the original company may have followed over them. This isn't the first time. I've seen it dozens of times, and I don't even specifically care about these two companies.
- slimsag 7y agoI don't think GP's comment was negging or passive-aggressive at all. The original GP said "That must make you nervous over at GitLab, no?" so it only seems rational to explain that they see this as validation and not as a risk. Somehow, you took this explanation of why they aren't worried about this and turned it into a passive-aggressive stance..