1. GitLab is heavy and slow compared to lightweight self‑hosted alternatives
“GitLab feels sluggish, and is bloated with 1001 thing I'd never use that just makes the UI a pain.” – prymitive
“The Ruby on Rails tax… every admin action you try to take on the backend is SLOWWWWW.” – 12_throw_away
“Power usage on the server dropped by 10% when I switched to Forgejo.” – NorwegianDude
2. Feature overload and a confusing UI make GitLab hard to use
“GitLab tries to be everything.” – shevy‑java
“The UI is one huge block of text on white background… action buttons buried in the middle of the page.” – prymitive
“Testing the CI/CD script on GitLab… it doesn't exist, and it's hell.” – paskejl
3. Subscription costs and the trade‑off between enterprise‑grade tooling and open‑source self‑hosting
“You need a subscription to use your subscriptions.” – davidee
“GitLab is pretty smooth sailing… but you have to pay for the premium features.” – gear54rus
“GitLab is a big boat in itself… but when you reach a certain org size it behaves well.” – flipped
These three themes—performance/resource demands, feature/UX complexity, and the cost/enterprise‑vs‑open‑source trade‑off—dominate the discussion.