zlacker

And it being open core (MIT) means spinning up a version to test something is incredibly easy. Not exactly resource cheap, as it's still a rails app with multiple servers "smuggled" in the docker image, but it is easy

And I have long held that they are hungry, shipping like clockwork on or about the 20th of every month, showing up with actual improvements all the time https://about.gitlab.com/releases/ It seems this month brings 18.0 with it, for whatever that version bump happens to include

They also have a pretty good track record of "liberating" some premium features into the MIT side of things; I think it's luck of the draw, but it's not zero and it doesn't seem to be tied to any underhanded reason that I can spot

>>mdanie+(OP)
Why gitlab hasn't been able to capitalize on GitHub's many failures is almost as interesting as GitHub's fall.

I think the GitHub brand is still stronger and people just don't "care" about gitlab.

>>bearde+jj
Yeah, it's almost certainly the network effect. Although poor GitLab isn't doing themselves any favors by picking what seems to be the slowest web framework one can possibly imagine

But, anytime I am empowered to pick, I'm going to pick GitLab 100% of the time because it has every feature that I care about and "being popular" isn't a feature that I care about