3 ms·
From my perspective, Gitlab needs to urgently reallocate 90% of its developper force from "Adding new features in 10 different axes" to "Stop adding new feature
by crubier 6y ago
From my perspective, Gitlab needs to urgently reallocate 90% of its developper force from "Adding new features in 10 different axes" to "Stop adding new features and exclusively work on performance and consistent unified UX".
I know it hurts, I know it's probably not what devs at Gitlab aspire to, but I believe it is much needed. Possibly, an entire rewrite of some core aspects are needed. I have a lot of trouble selling Gitlab to my team. Everyone just wants to move to Github to have a simple UX that works.
- sofixa 6y agoTheir best shot at competing with GitHub is on features ( and they do a pretty good job at it too), so i think they can't afford to stop shipping new features. GitHub's UX is simple because it doesn't even come close to what GitLab provides, even in the free tier, and their iteration is much slower. If GitHub had GitLab's features it'd have a complex in some places UX as well.
- wingerd 6y agoThey have no clue how to fix performance issues. These performance issue have been there for multiple years and users have been asking them to fix these. Instead, their core competency seems to be hire people to advertize and post "thank you" and "we are here to address your issues" kind of messages here at HN. They have a whole army of those users here (you can check past HN threads related to gitlab).