So, in the Swift world, I presume a lot of people prefer to remain “Swifty”. That is, why would you opt for old Objective-C libraries? Out with the old, in with the new!
So, we adopt Alamofire. Is it just me, or is this library a bit unwieldy? I think it has a lot to do with Swift shorthand and often not knowing just what types are actually being passed around, especially given autocomplete.
On top of that, just when you get your head around a specific release, they make a new major release, breaking old APIs. And if I’m going to have to keep updating my code to stay current because “out with the old, in with the new”, why don’t I just stay with AFNetworking? I mean come on. It’s networking. For the mostpart it’s just “give me that data at that URL. Here’s my auth info.” Done. Or “here’s some data for you. Here’s my auth info.” Done.
Anyway, it’s a rant. I just don’t find Alamofire all that sexy. It reminds me of dealing with civil servants. The creators imagined this bureaucratic utopia that functions perfectly as long as everyone understands it. Furthermore, we must not only understand it, but are fully on board with its vision. Meanwhile, we the people are busy trying to write our own apps, and couldn’t really care less. We just want to get data and post data and not have to deal with too much crap in the middle.
(Go ahead, snarky programmer. Now tell me off, tell me to just use this, that, or the other. Reject my feedback. It’s fine. All I’m saying is that AFNetworking seemed a lot easier to use.)