Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Alamofire: HTTP Networking in Swift

github.com

Post reply on HN
Print view View original

21–29 of 29 posts

Re: Alamofire: HTTP Networking in Swift

#22

Post by inglor »

matttthompson wrote: post #2

Creator of Alamofire here. Just pushed the 1.0.0 release. Happy to answer any questions you might have.

What about supporting using something like PromiseKit for error handling and interoperability with aggregation methods? Would you be willing to consider that?

Thanks for your work by the way.

Re: Alamofire: HTTP Networking in Swift

#24

Post by matttthompson »

inglor wrote: post #22
matttthompson wrote: post #2

Creator of Alamofire here. Just pushed the 1.0.0 release. Happy to answer any questions you might have.

What about supporting using something like PromiseKit for error handling and interoperability with aggregation methods? Would you be willing to consider that? Thanks for your work by the way.

I don't really see much need for it. Others are welcome to create such an integration, but I probably won't do so myself.

Re: Alamofire: HTTP Networking in Swift

#25

Post by teacup50 »

Void_ wrote: post #12
treve wrote: post #4

Congrats on this release! 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 :). There seems to be a lot of new general-purpose libraries with very poor non-descriptive names coming out. 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…

I wonder how much this matters to other developers – but I, at least subconsciously, when faced with a library choice, take into account things like: - Simple, pretty name (Alamofire is very nice-sounding and memorable – even feels like overkill, author should've saved it for an iPhone app or something.) - The pretty logo - The perfect use of Markdown (I'm so obsessed about using `` around everything that looks like…

> There must be correlation between the presentation and quality of the source code!

There isn't.

The overlap is relatively small between:

- People who are great at writing software.

- People who are great at designing logos and quality of presentation (or have someone on staff that is).

Re: Alamofire: HTTP Networking in Swift

#26

Post by inglor »

matttthompson wrote: post #24
inglor wrote: post #22

Earlier quoted context omitted.

What about supporting using something like PromiseKit for error handling and interoperability with aggregation methods? Would you be willing to consider that? Thanks for your work by the way.

I don't really see much need for it. Others are welcome to create such an integration, but I probably won't do so myself.

Aggregation of multiple requests with centralized error handling would be really nice, I guess that could be built from the outside though.

Re: Alamofire: HTTP Networking in Swift

#27

Post by qrush »

matttthompson wrote: post #2

Creator of Alamofire here. Just pushed the 1.0.0 release. Happy to answer any questions you might have.

Hey Matt! A few:

* Is this being used in any apps in the App Store currently by you? (or Panic?)

* Is Alamofire a non-profit or some kind of organization? Curious why it's listed in the README.

* Perhaps a bit deeper: Why a rewrite of AFNetworking's feature set instead of a AFN 3.0?

Post reply on HN