4 ms·
> I've also never felt compelled to use Gitlab. They literally offer no significant advantage other than being an alternative to Github. I completely disagree.
by chipdart 2y ago
> I've also never felt compelled to use Gitlab. They literally offer no significant advantage other than being an alternative to Github.
I completely disagree. GitLab undoubtedly has the best CICD service. GitHub Actions feel poorly designed and half-baked in comparison to the point they barely feel prod-ready.
It's interesting to read into the thought process of anyone picking GitHub vs GitLab, because, other than being the default with tolerable shortcomings beyond copilot, there is no compelling reason to pick GitHub.
If anything, GitLab's Achilles heel is it's massive Product Management problem. I recall that access to some features like Group Access Tokens were unexplainably removed from free access without updating documentation or even it's UI. Apparently some GitLab PM made a call to pull them out without bothering to check for the customer impact loose ends, and all loose ends were simply left in place for customers to repeatedly pester support without any action.
- tempay 2y agoI use both extensively and lean towards to opposite statement, though not as strongly. GitHub Actions feels much more well thought out to me. The templating feels less hacky and the workflows via "uses" work really nicely for abstracting common bits of CI config into "packages". The downside is that GitLab CI feels easier to pick up and explain. On the opposite side, GitLab CI feels like it was made for containers and k8s whereas GitHub Actions feels like it's just a VM (even if the runner software is technically more flexible than that). From a management perspective GitLab is nicer but as a user I often want to avoid thinking about any of the k8s quirks and just have an emphemerial VM to play with.