But to be honest I do see the point of the author. Either stop "half-assing" GitLab.com or remove the product (GitLab.com) entirely (and focus only on self-hosting customers (GitLab Enterprise Edition)) might be a better decision in the long run.
But I am sure no one on management level wants to do this decision. So you half-ass a product.
This kind of situation can be frustrating for people working on the product itself (at least when they care). And each new developer that joins the product will probably suggest: "Oh we should care more about scalability." And each senior will be: "yeah yeah, i know..."
Gitlab.com is a marketing instrument and if you 'remove the product entirely' then the enterprise edition will sell only a small fraction of what it sells today.
I do not know if your statement holds true. But you shouldn't half-ass a marketing instrument either IMHO.
That I agree with. There are some weird incentives at work though: a commercial user of Gitlab.com might see their frustration with Gitlab.com as the reason to go for an enterprise license rather than to switch to the competition.
If Gitlab.com is a money losing product why is it the same price as the self-hosted option.
I literally bought licenses from gitlab before realising that the seat cost is the same if I let them host it or we do it. So why take the infrastructure cost?
You have more control on the data. Isn't that why you self hosted it in the first place?
Re:What it was like working for Gitlab
by insensible on Sunday February 11, 2024 @06:16AM
(#39334237)
Yes, it’s a mistake to design your company’s output in a way that results in shipping a defective product.
Re:What it was like working for Gitlab
by foobarbazboff on Sunday February 11, 2024 @07:01AM
(#39334439)
Is it a defective product, or is it a fully-featured demo that is just good enough to show companies what they could have if they host the software themselves? "You get all these features, plus all the speed and security that comes with running this in your own corporate environment"
Why buy the cow when you can get the milk for free?
Re:What it was like working for Gitlab
by fred_is_fred on Sunday February 11, 2024 @11:26AM
(#39336076)
I’d guess because many IT departments figure that on-premise=secure and provides them the illusion that they can prevent source code from leaking this way.
Is that really a mistake, then? As a first approximation, company has to invest in the thing which makes money, not the thing which loses money. Now, higher-order thinking might suggest that a more-performant gitlab.com might bring in more customers, build a stronger reputation and so forth. Still, if the company’s real business is selling self-hosted software, it makes sense to focus development resources on self-hosted software.