matttthompson

6 ms·

1.
by matttthompson 11y ago
And to be clear—these are all existing sample apps for open source Objective-C projects. The creator of this site does not appear to have done anything but gathered these up into zip files. The complete lack of attribution is misleading.
2.
by matttthompson 11y ago
I don't understand why this is getting so much attention. This is nothing more than a couple zip files containing a few Objective-C open source projects that happen to have example projects. As far as I can tell, the only original cont
3.
by matttthompson 12y ago
I have no illusions about the amount of effort and investment necessary to change technology stacks. Carbon was only officially deprecated in OS X 10.8. To speak of the death of technology is only to acknowledge that it is mortal. My claim
4.
by matttthompson 12y ago
I appreciate your feedback, but I think you're reading an entirely different argument than what is presented in the article. It's not that everything is going to be rewritten in Swift (I'm not sure where you got that idea). R
5.
Developing with Pay on iOS(nshipster.com)
15 points by matttthompson 12y ago|0 comments
6.
by matttthompson 12y ago
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.
7.
by matttthompson 12y ago
You make some good points, and I agree to caution against names that bear no semantic relationship with their purpose. My justification of Alamofire is that it reflects the history of the project, which traces back from AFNetworking to Gowa
8.
by matttthompson 12y ago
> Was there any reason why you chose callbacks over a Promise-like pattern for the async responses? Deeply-nested networking callbacks are a code smell, and I find that promises often do more harm by hiding those smells—or worse, obscuri
9.
by matttthompson 12y ago
Yes, that's correct.
10.
by matttthompson 12y ago
The short answer: Use the version of `request` that takes a `URLRequestConvertible`, and specify the header fields in that. The long answer: Custom headers on a per-request basis are a bit of a red herring, from an API design perspective. I
11.
by matttthompson 12y ago
Creator of Alamofire here. Just pushed the 1.0.0 release. Happy to answer any questions you might have.
12.
Alamofire: HTTP Networking in Swift(github.com)
99 points by matttthompson 12y ago|28 comments
13.
by matttthompson 12y ago
Author of the article here. Let me know if you have any questions or feedback.
14.
// MARK: is the new #pragma (…and other changes to documentation in Swift)(nshipster.com)
1 points by matttthompson 12y ago|0 comments
15.
Syntactic Icing with Swift Custom Operators(nshipster.com)
1 points by matttthompson 12y ago|0 comments
16.
by matttthompson 12y ago
> ...ending up in an error block because of a malformed server response is a pain in the ass. Is it really an error if you get a 200 OK response but the body isn't valid JSON? Yes. Oh goodness, yes it is. Having consistent validatio
17.
by matttthompson 12y ago
Nothing in AFNetworking forces a success/failure block. For request operations, `completionBlock` can be set directly. For session tasks, the parameter is a `completionHandler`.
18.
by matttthompson 12y ago
There's plenty of room for simplicity and abstraction, but this is not a particularly good one, if I'm going to be honest. I can't think of any situation in which I'd recommend this over either AFNetworking or the built-
19.
by matttthompson 12y ago
> If i want to generate url requests, i have to use a serializer class... No, you don't. There's nothing stopping you from creating `NSURLRequest` directly. > ...wouldn't it be better to just expose all the setup functi
20.
by matttthompson 12y ago
I'm all about seeing new ideas about how to approach networking architectures, but this one makes me worried for anyone who decides to adopt it. Networking is an inherently complex problem. Attempting to simplify the problem by ignorin
21.
Xcode Plugins(nshipster.com)
2 points by matttthompson 12y ago|0 comments
22.
$1 Million(mattt.me)
2 points by matttthompson 13y ago|0 comments
23.
Xcode Launch Arguments & Environment Variables(nshipster.com)
1 points by matttthompson 13y ago|0 comments
24.
by matttthompson 13y ago
In my opinion, no better case for AFNetworking 2.0 wrt/NSURLSession can be made than AFURLSessionManager, and all of the great stuff it does for you. http://cocoadocs.org/docsets/AFNetworking/2.0.0/Classe
25.
by matttthompson 13y ago
Yes, AFNetworking 2.0 (with the exception of `NSURLSession` functionality) is compatible with iOS 6 and Mac OS X 10.8. (This was changed from the original plan to only target iOS 7, after it was determined that A) only the two classes neede
26.
AFNetworking 2.0(github.com)
135 points by matttthompson 13y ago|18 comments
27.
ASCIIwwdc: Searchable full-text transcripts of WWDC sessions(asciiwwdc.com)
37 points by matttthompson 13y ago|10 comments
28.
Obscure APIs in iOS 7: Smile Detection, Speech Synthesis & QR Code Scanning(nshipster.com)
2 points by matttthompson 13y ago|0 comments
29.
Rocket: a hybrid approach to real-time cloud applications(rocket.github.io)
4 points by matttthompson 13y ago|0 comments
30.
Creating DSLs in Objective-C with Object Subscripting(nshipster.com)
3 points by matttthompson 13y ago|0 comments

More ›