Tuist VS Alamofire

At my current workplace, we use Tuist. It's a great tool, but there are 20 of us, so it's necessary. In smaller teams (up to 5-7 people) I didn't feel like there were huge problems with .xcodeproj. Sure, some conflicts now and then, but far from every time you merge something. https://github.com/tuist/tuist

Tuist Projects ('Project.swift'), Swift packages ('Package.swift'), and barebone xcodeproj are now supported.

On a project I worked on I transitioned the codebase to a micro framework setup using tuist.io.

I think the hate comes from seeing its unresponsiveness and slow builds in large-scale projects. Everything works great in a recently-creates project until your project turns into a complex dependency graph of targets with intricate and inconsistent build settings. That’s the main reason why we are building https://tuist.io

Curious why you guys built XCodeJS instead of going with XcodeGen or Tuist

Alamofire is a swift http request lib. By default, we need use completion handler to handle response. Today we are going to find out how to use it with async and await.

Looks like your Alamofire tutorial is out of date. I suggest you read the current documentation and update your code. For instance, you can update your example to:

Alamofire - Elegant HTTP networking

Alamofire - Alamofire is an HTTP networking library written in Swift. (de facto standard library for network) Language: Swift.

You can find an example using Alamofire, the most commonly used network framework, here.

https://github.com/Alamofire/Alamofire/blob/master/Documenta...

To add Alamofire, we'll be using Swift Package Manager. Xcode comes with built-in support for it and we'll not have to use external package managers like Cocoapods or Carthage. Click on File → Add Packages...