> Isn't gitlab highly concerned with a new company starting a similar product in a more efficient language implementation and eating your lunch? I'm nobody but

> Isn't gitlab highly concerned with a new company starting a similar product in a more efficient language implementation and eating your lunch? I'm nobody but my two cents is that this falls under the category of things we shouldn't worry about because there isn't much we can do about it. I am sure Gitlab is concerned but I would say it doesn't matter because this is a problem you can probably throw hardware at (repo A going down will likely not affect most repo B users). I imagine of course gitlab.com would want to make the most of the hardware it has and I'd love to read about the cost of porting gitlab to a "more efficient" language implementation but I hope they're more concerned about delivering value to users than worrying about how to fend off competition. This might be unpopular here but I hope Gitlab does all it can to keep their cost low even if it means slightly lower salaries.