XcodeBenchmark VS Alamofire

I’m a software developer as well and I ended up ordering a m3 max (still not received though). Main reasons against the m3 pro was the lesser number of performance cores compared to previous gens and slower memory bandwidth. Indeed, in this Xcode benchmark used by the Max Tech channel, the m3 pro compiled code slightly slower than the M1 Pro. Probably is a corner case but I think it’s worth to mention.

I found only one reasonable benchmark comparing compilation speed for large projects here. Does anyone have experience with these 2 machines for backend development with compiled languages?

Here's repo you should look at when buying a MacBook. Difference between M2 Pro and M2 Max is ~15%.

I'm not sure about AI/ML dataset training performance, but this XcodeBenchmark performance appears to be very comparable between the M2 and M2 Pro.

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...