3 ms·
I'm glad you brought up Docker, but I think this is a move against GitLab, more than it is against NPM or Docker. Lots of us use GitLab at work because it's su
by keytarsolo 7y ago
I'm glad you brought up Docker, but I think this is a move against GitLab, more than it is against NPM or Docker.
Lots of us use GitLab at work because it's such a complete product. Source code, container registry, CI/CD, Issues (via GitLab or Jira), Maven repository, NPM repository, etc. etc.
Microsoft is trying to build out GitHub so that they can more effectively compete for GitLab's corporate customers. Since buying GitHub they've added many of GitLab's key features to GitHub and these are some of the biggest adds so far.
You might be right that this hurts NPM and Docker, but I think it'll hurt GitLab more.
- orthoxerox 7y agoThe price of self-hosted GitHub was so high the last time I checked that you could buy the whole Atlassian stack or the highest tier of GitLab instead and still have enough money left for Artifactory.
- gmueckl 7y agoI guess that's their way of telling your bean counters that you don't want self-hosted and instead want to put everything on their servers (<Jedi mind trick wave>). That way, they can increase lock in.
- GordonS 7y agoMicrosoft's Azure DevOps already has everything corporate customers could want though - AD integration, CI/CD (even hosted MacOS build agents!), choice of TFVC or Git, task boards, testing stuff...