4 ms·
It feels to me like GitLab might be shooting themselves in the foot by spreading their resources too thin, too quickly. They have the very grand ambition to ta
by fro0116 9y ago
It feels to me like GitLab might be shooting themselves in the foot by spreading their resources too thin, too quickly.
They have the very grand ambition to take over the entire devops toolchain from source control to deployment, and some parts of the toolchain can certainly benefit from the tight vertical integration that GitLab provides, and when everything just works the product does end up providing a very streamlined user experience.
However, this also means that their monolithic toolchain has to be able to out-compete best-of-class specialized tools in every part of the chain, and every part of the chain where they fail to do so could end up as a potential dealbreaker for a large subset of their user base.
I've used GitLab.com for a few projects, and in general I've found the various aspects of their product sorely lacking in terms of overall polish, performance, and capability compared to excellent specialized products like GitHub for VCS, CircleCI for CI/CD, and Pivotal Tracker for project tracking/planning, etc.
Also, the fact that they're trying to take over the entire toolchain means that just about everybody else in the devops space sees them as a direct competitor, so until they grow to become an 80-pound gorrila that nobody can ignore in at least 1 part of the toolchain, very few other companies building devops tooling will willingly integrate with their product, which makes them even less attractive for users with specific/more advanced needs that their product alone can't meet.
With all that said, I really appreciate their dedication to open-source and am personally rooting for their success, but I can't help but shake the feeling that they're fighting a losing battle. DevOps tooling is simply too diverse, complex, and opinionated a field for any 1 company to dominate from end-to-end. Focusing resources to become the best tool for the job in 1 area and using that leverage to foster an open-ecosystem around that product seems like a much more viable long term strategy (though that could certainly prove to be difficult if you're trying to become the best tool for VCS, due to how entrenched GitHub is in terms of developer mindshare).
- sytse 9y agoWe are very afraid of spreading ourselves too thin too. Recently we've been encouraged by how GitLab CI is doing, it is winning developers gitlab-ci-is-the-most-popular-next-generation-ci-system and industry analysts over https://about.gitlab.com/2017/09/27/gitlab-leader-continuous-integration-forrester-wave/ https://about.gitlab.com/2017/09/27/gitlab-leader-continuous... I think what makes GitLab different is that more than 1800 people contributed to it to increase the depth. Our team members are focussed on increasing the breath. From https://about.gitlab.com/strategy/ https://about.gitlab.com/strategy/ "We realize our competitors have started earlier and have more capital. Because we started later we need a more compelling product that covers the complete scope, that is integrated out of the box, and that is cloud native. Because we have less capital, we need to build that as a community. Therefore it is important to share and ship our vision for the product. The people that have the most knowledge have to prioritize breadth over depth since only they can add new functionality. Making the functionality more comprehensive requires less coordination than making the initial minimal feature. Shipping functionality that is incomplete to expand the scope sometimes goes against our instincts. However leading the way is needed to allow others to see our path and contribute. With others contributing, we'll iterate faster to improve and polish functionality over time. So when in doubt, the rule of thumb is breadth over depth, so everyone can contribute."