Comment by ksec
4 hours ago
>Speed. The GitLab web interface has always felt sluggish to me.
10 years later the same problem remains. While Gitea / Forgejo have very little performance problems. And will only get better once Go 1.26 is out. Which is a much bigger release than a single digit version number upgrade.
I used GitLab only as a remote repo for private projects, no CI at all. The laggy interface and that damn browser check every so often made me close my account.
It must be a fundamental architectural problem with Gitlab. When I had to use it for work the speed killed me. Especially searching for issues. I will never consider gitlab for anything until they find a way to boost performance.
The Ruby on Rails tax. It isn’t impossible to make snappy apps with it, but it must be uneconomical in terms of dev costs because no one does.
Just like a truck will always be more sluggish than a small car. They are very different beasts where one is aimed at enterprises and the other one for small projects without all the corporate needs.
The enterprise version is just as slow.
I thought they're only struggling with the free public version, but no. GitLab run on a private box is the same bag of lags and loading spinners.
I'm not talking about GitLab enterprise vs. GitLab free. It's about GitLab vs small projects like Gitea / Forgejo mentioned in the parent comment.
I just wish they had sub/project folders like in gitlab. I would switch in a heartbeat.