Someone send gitlab a box of tissues. And another box full of competent sysadmins.
The market figured out Gitlab’s secret
11–20 of 71 posts
Re: The market figured out Gitlab’s secret
#12What a strange post. GitLab is under siege from GitHub. The argument for GitLab has always been that they are more feature-rich, the argument for GitHub has been that their uptime is >80% and their UX is excellent. If GitHub achieves feature parity, GitLab is dead.
Unless you trust the GitLab team to be better than Microsoft owned GitHub
Re: The market figured out Gitlab’s secret
#13This seems like misdirection. Gitlab's largest problem is their record of operational incompetence. This will take some time to recover from. Personally, I won't use them for a least two more years, based on their data loss incident two years ago.
I do wish them luck. Github/Microsoft should have a credible competitor.
Re: The market figured out Gitlab’s secret
#14Every time github releases a feature this is the response. These posts are so pathetic. I’m surprised that they continue to play this angle. It’s a very polarizing way to address the community that will definitely continue to stir up us vs them mentality between GitHub and Gitlab users.
Everything I hear about them screams immaturity, from deleting their prod db to smack talking competitors.
Not to heap it on...but ok who am I kidding I am heaping it on: I had a terrible interview experience with them.
Basically there was a period on HN where every other post was about stupid hiring practices and how absurd some code interviews were. Well Gitlab embodied all of them.
They phone interview quizzed me on several "gotcha" questions, and finally I was asked to describe Prototypical inheritance (JS), in which I was knowledgeable about and gave a very detailed and technical answer, in my own words (so not some memorized wikipedia answer), and basically what I got back from the recruiter was in essence, "Nope that's not what this piece of paper I have in front of me says the answer is" that is that although I had answered the question technically correctly, it wasn't the type of answer they were looking for.
Anyways, not salty about it anymore because it seems like I dodged a real bullet.
Re: The market figured out Gitlab’s secret
#15Some will continue to prefer a self-hosted GitLab instance over GitHub, but requiring at least 4GB of RAM [1] for a low traffic instance sounds like an aberration. There should be better ways to manage memory consumption, and a lean GitLab instance that we have full control over could still be their selling point over GitHub. [1] https://docs.gitlab.com/ce/install/requirements.html#memory
Giving away your core product for free is hardly a “selling” point. As open source is all about scratching your own itch, their itch isn’t lean software because that isn’t what they run in their company.
Re: The market figured out Gitlab’s secret
#16Every time github releases a feature this is the response. These posts are so pathetic. I’m surprised that they continue to play this angle. It’s a very polarizing way to address the community that will definitely continue to stir up us vs them mentality between GitHub and Gitlab users.
GitLab don't have to worry too much. Their uptime has been fine for us over the course of several years. And it's good that GitLab is around, so that we don't have to worry quite so much about Microsoft/GitHub messing around with the code in international projects. They have a great history[1] of co-operating with nefarious people. (And no, most people do not sign their commits and watering hole attacks are an obvious worry).
Re: The market figured out Gitlab’s secret
#17I think what GitLab really needs is what a lot of open source projects are lacking: popular community forks. Their product development benefits from the community's QA feedback, but there are no community forks (that I am aware of) that are taking GitLab CE in directions that gitlab-org won't go. IO did this for Node and everyone has benefitted.
I think GitHub's UX has caused new developers to lose true meaning of fork. When software doesn't work the way you want it to, you fork it, and if other people want it enough, they will merge it into their own forks and maybe some day it will get adopted upstream.
Re: The market figured out Gitlab’s secret
#18Some will continue to prefer a self-hosted GitLab instance over GitHub, but requiring at least 4GB of RAM [1] for a low traffic instance sounds like an aberration. There should be better ways to manage memory consumption, and a lean GitLab instance that we have full control over could still be their selling point over GitHub. [1] https://docs.gitlab.com/ce/install/requirements.html#memory
We agree 4GB is too much. We put a team together to get the memory usage down https://about.gitlab.com/handbook/engineering/development/en... They’re rolling Puma out as an application server on .com within weeks. After that is successful we’ll make that the default. That should save a lot. After that the memory team will keep improving it.
Re: The market figured out Gitlab’s secret
#19What a strange post. Considering the timing, it seems like it must have been posted in response to GitHub's announcement of new CI/CD functionality (also on the HN front page): https://github.blog/2019-08-08-github-actions-now-supports-c... But if so, it's quite a backhanded response – the post itself only mentions GitHub in passing.
They're constantly passive aggressiveness about it like this
Re: The market figured out Gitlab’s secret
#20I think what GitLab really needs is what a lot of open source projects are lacking: popular community forks. Their product development benefits from the community's QA feedback, but there are no community forks (that I am aware of) that are taking GitLab CE in directions that gitlab-org won't go. IO did this for Node and everyone has benefitted. I think GitHub's UX has caused new developers to lose true meaning of fo…
We had companies forking GitLab instead of contributing upstream, they all fell behind with upstream and couldn’t keep up to date anymore.
Any examples of things you see that we at GitLab Inc. are not open to?