mattdonnelly

4 ms·

1.
by mattdonnelly 12y ago
It is actually, but functions like the one mentioned above are bindings for Objective-C / C functions and share the same name as the function they bind to
2.
by mattdonnelly 12y ago
Almost all of Apple's frameworks written in Objective-C and C are incredibly verbose. It's just an adopted style of the language and although it's often a little difficult to look at, it can be quite helpful sometimes
3.
by mattdonnelly 12y ago
Most of problems I encountered while writing this came from Swift's interoperability with Objective-C. It can often be difficult to work with and takes a while to get used to. I actually think it would be worth developers considering
4.
by mattdonnelly 12y ago
The processes for creating frameworks in Swift is pretty much the same as with Objective-C. That said Xcode 6 has made it much easier to handle distributing frameworks for different devices
5.
by mattdonnelly 12y ago
This was actually part of something else I've been working on rather than attempt at deliberately reinventing the wheel. That said, I do think there's some benefit in rewriting existing Objective-C frameworks in Swift as Swift&#x2
6.
Swifter – A Twitter Framework written in Swift(github.com)
29 points by mattdonnelly 12y ago|18 comments
7.
by mattdonnelly 13y ago
This is a simple little app I've been working for the last few months. Some of the features include: - Two Viewing Modes: Grid and List. - Browse all of your feeds including popular, everyone and debuts - User login, so you can view yo
8.
Basket for iPhone: The Definitive Dribbble Client(getbasketapp.com)
6 points by mattdonnelly 13y ago|1 comments
9.
by mattdonnelly 13y ago
Nothing you said is factually wrong but you're being obnoxiously pedantic and rude. OP was merely commenting on the similarities between his and John Carmack's approach to solving the problem and is in no way deluding himself by c
10.
by mattdonnelly 13y ago
Christ, you sound like such an insufferable prick