Congrats on this release!<p>However, I think the library name is a bit of a poor choice. I don't want to take away your thunder, I just picked this post to do my rant :).<p>There seems to be a lot of new general-purpose libraries with very poor non-descriptive names coming out.<p>Whenever I need to dive into a new codebase, in a language and ecosystem I'm unfamiliar with, it's extremely hard to figure out which dependency and library does what. I was tasked to dive into a massive RoR application recently, and I ended up having to write a glossary first to remember what every non-descriptive noun implied.<p>After getting familiar with a particular language's ecosystem, this problem becomes tends to go away, and as a library writer, it becomes easier to fall into the same trap by picking a name that's marketable and distinct.<p>But I feel we're collectively making it increasingly harder for people to ramp up in new ecosystems and maintain future legacy codebases.<p>For names of large applications this is not as bad, and some of these applications become household names, but I think we should try to avoid this for general-purpose utilities.
Thanks for your great works! I am using Alamofire on my project right now. Do Alamofire support or will support async image loading via URL just like AFNetworking? I can't find the API anywhere on the docs.