GitLab vs. Xcode

It is well-suited for any project that needs VCS. It's an excellent choice for teams that might be remote or have to collaborate across teams. Plenty of features allow for async working. With its dashboards and reporting features, it is also suitable for nontechnical PMs or stakeholders. It allows for very bespoke customization and can most often do much more than you need it to.

Incentivized

We are huge advocates of native iOS development and there is just real alternative when it comes to developing in Swift or Objective-C for the iPhone and iPad

Incentivized

• GitLab excels in managing code versions, allowing easy tracking of changes, branch management, and merging contributions.
• It helps maintain code stability and reliability, saving time and effort in the development or research workflow.
• Powerful code review features, enabling collaboration and feedback among team members.
• Robust project management features, including issue tracking, kanban boards, and milestones.

Incentivized

• Debugging
• Profiling
• Great IDE

Incentivized

• CI variables management is sometimes hard to use, for example, with File type variables. The scope of each variable is also hard to guess.
• Access Token: there are too many types (Personal, Project, global..), and it is hard to identify the scope and where it comes from once created.
• Runners: auto-scaled runners are for the moment hard to put in place, and monitoring is not easy.

Incentivized

• Documentation
• Number of settings can be overwhelming
• Embedded help for settings and configuration
• Templates
• Collaboration
• Managing of credentials (although this has recently gotten better)

Incentivized

I really feel the platform has matured quite faster than others, and it is always at the top of its game compared to the different vendors like GitHub, Azure pipelines, CircleCI, Travis, Jenkins. Since it provides, agents, CI/CD, repository hosting, Secrets management, user management, and Single Sign on; among other features

Incentivized

I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!

Incentivized

Xcode occasionally exhibits some behaviors that are hard to explain, but are generally cleared by restarting the program. In an application this large and complex, I suppose this is somewhat expected. The sheer vastness of the frameworks collection has to be a huge management issue all by itself. However, those breaks in the flow can have impact on developer productivity.

Incentivized

I've never had experienced outages from GItlab itself, but regarding the code I have deployed to Gitlab, the history helps a lot to trace the cause of the issue or performing a rollback to go back to a working version

Incentivized

Since we don't use the cloud based features of Xcode, it is basically available 24/7 for us. We don't need the extended compilation features that are offered in the cloud as our projects to this point have not been that large or complex. We have never seen a wholesale breakdown of Xcode availability at any point in our use of the product.

Incentivized

GItlab reponsiveness is amazing, has never left me IDLE. I've never had issues even with complex projects. I have not experienced any issues when integrating it with agents for example or SSO

Incentivized

Every developer wants faster compiles, but that can be achieved by either going to the cloud or by provisioning the local station to a higher powered configuration. My only minor complaint is the amount of local mass storage that Xcode as a system consumes. This makes it interesting to set up a development environment on a midrange laptop, however it is easily managed with external storage at a reasonable price.

Incentivized

At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft

Incentivized

GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution. GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same. No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.

Incentivized

Xcode is the clear choice in general circumstances in Apple echosphere application development (for instance, not for Java or web programming necessarily) primarily due to the fact that it is Apple's in-house tool. It received a lot of attention and is used by a huge audience of developers. It has the advantage of being free, heavily supported by Apple, tightly tied to OS and hardware changes, and benefits from significant Apple Intelligence enhancements in the latest version.

Incentivized

I think is very well designed, and like any VCS it works as intended

Incentivized

Xcode only loses points due to the occasional situation where it manages to somehow tie itself into a knot and starts to exhibit odd symptoms. This is almost always solved by simply saving progress and restarting the environment. Fortunately, that doesn't happen too frequently and is easily repaired while taking a short break to walk around and stretch.

Incentivized

• GitLab cut down our spent on container, package and infrastructure registry
• Best thing is we can now have everything in single platform which cost effective too
• Quality of support is really good and they do have emergency support team as well which is great

Incentivized

• Xcode is free, and is supported at low cost by individual or organizational membership
• There are a lot of free resources available, which is particularly important to students and independent developers
• Since producing apps is not a core business function of the university, it is difficult to provide direct bottom-line tangible benefits, but frequently programming students come in with a basic understanding of Xcode already in place, which saves class time
• Producing standard structured code from a standard IDE makes it easier for sharing code with peer institutions
• Students expect to have university branded "helper" apps available, and Xcode makes it fairly easy to transport code from one contractor to another
• No negative impacts are immediately evident other than familiarization time with the IDE can be high if you try to know what everything does

Incentivized