Explore >> Select a destination
|
You are here 
|
ashishkakkad.com | ||
| | | | |
sintraworks.github.io
|
|
| | | | | Recently I started studying Ray Wenderlich's tutorial book RxSwift. Early on, the book suggests using Rx as an alternative to delegates and their associated protocols. I though, great, but, for the task at hand, that's a rather heavy handed solution. (Yes, I know it is just an example designed to teach me the basics.) So I tried to imagine how I could achieve something similar to the functionality they built for their initial examples, without the overhead of importing a big library like RxSwift. | |
| | | | |
www.cs.cornell.edu
|
|
| | | | | I did some iOS programming recently (for an unknown reason). Using the new Swift language has made it evident the language is young-and, like a rebellious teenager, it conflicts with its much older framework counterpart, Cocoa. Here are two places where the disconnect is most stark, and where Swift should grow more sophisticated type-system features. | |
| | | | |
swiftrocks.com
|
|
| | | | | Global functions, or functions that can be accessed from anywhere without the scope of a specific type is an old concept that was popular in languages like C and Objective-C, but unrecommended in Swift as we would rather have things that are nicely typed and scoped ( | |
| | | | |
toddmoore.com
|
|
| | | I received a couple e-mails asking to explain my "horrible experience" with developing for Windows Phone 7. This is in response to my quote in a CNN storyreported by Mark Milian. The horrible experience wasn't in the development of the application for WP7, but it was in the publishing of the application to App Hub. [...] | ||
