3 ms·

It's a shame that Gitlab isn't profitable. Maybe it's just because I have to use it for work and am therefor familiar, but I've always slightly preferred it to

It's a shame that Gitlab isn't profitable. Maybe it's just because I have to use it for work and am therefor familiar, but I've always slightly preferred it to Github. I also never really saw Github enterprise server being viable in the "we have to self host for security reasons" space, but maybe someone else has a different view.

pm90 2y ago
We ran github enterprise on our infra for several years. It was a pretty low overhead thing to run except if you’re really big. The nice thing was that we could customize the api rate limits which is really annoying with saas github.
lvncelot 2y ago
The CI/CD alone in Gitlab is light years ahead of what Github has to offer. I'm really hoping that they can hold on in some way or that the core open source application stays viable.
- orf 2y ago
  How is it light years ahead? I feel exactly the opposite way
  - lvncelot 2y ago
    It's way more powerful. Something like dynamically generated child pipelines doesn't even have any equivalent in GitHub Actions.
    - orf 2y ago
      True, however on the other hand something truly basic like “not spending time re-compressing and re-uploading a cache after a cache hit”, “use zstd with caches”, or even “add fucking timestamps to CI logs” doesn’t even have any equivalent in Gitlab CI. Some might even say dynamically generating child pipelines, while cool, is a niche bandaid for some of the legacy tempting baggage they are unable to escape from that dramatically increases pipeline complexity whilst common use cases are still broken and still underserved. It’s a janky pile of unnamespaced, hard to debug and fragile YAML-template-meta-programming hacks. Light years my ass.
everfrustrated 2y ago
The other big reason to self-host GitHub is avoiding their constant outages. Controlling availability is a real benefit for larger companies (dev downtime) and those who need to be able to fix bugs in prod (roll forward) without being beholdent to GitHub's availability.

pm90 2y ago

We ran github enterprise on our infra for several years. It was a pretty low overhead thing to run except if you’re really big. The nice thing was that we could customize the api rate limits which is really annoying with saas github.

lvncelot 2y ago

The CI/CD alone in Gitlab is light years ahead of what Github has to offer. I'm really hoping that they can hold on in some way or that the core open source application stays viable.

orf 2y ago
How is it light years ahead? I feel exactly the opposite way
- lvncelot 2y ago
  It's way more powerful. Something like dynamically generated child pipelines doesn't even have any equivalent in GitHub Actions.
  - orf 2y ago
    True, however on the other hand something truly basic like “not spending time re-compressing and re-uploading a cache after a cache hit”, “use zstd with caches”, or even “add fucking timestamps to CI logs” doesn’t even have any equivalent in Gitlab CI. Some might even say dynamically generating child pipelines, while cool, is a niche bandaid for some of the legacy tempting baggage they are unable to escape from that dramatically increases pipeline complexity whilst common use cases are still broken and still underserved. It’s a janky pile of unnamespaced, hard to debug and fragile YAML-template-meta-programming hacks. Light years my ass.

everfrustrated 2y ago

The other big reason to self-host GitHub is avoiding their constant outages. Controlling availability is a real benefit for larger companies (dev downtime) and those who need to be able to fix bugs in prod (roll forward) without being beholdent to GitHub's availability.