Erica Sadun

I would add Erica Sadun to this list. She's been my go-to authority for all things ObjC (and now Swift) since 2008. http://ericasadun.com/

I'll add a few of my favourites: - iOS Dev Weekly (https://iosdevweekly.com/) - Little Bites of Cocoa (https://littlebitesofcocoa.com/) - objc (https://www.objc.io/) - NSHipster (http://nshipster.com/) - NSBlog / Friday Q&A from Mike Ash (https://www.mikeash.com/pyblog/) - This Week in Swift (https://swiftnews.curated.co/) - Erica Sadun (http://ericasadun.com/) - Quality Coding (http://qualitycoding.org/) - Use Your Loaf (http://useyourloaf.com/) - Swift Monthly (http://swiftmonthly.com/) - Cocoa, Objective-C and Swift programming News aggregator (https://twitter.com/cocoadevblogs)

Hopefully me too :) http://puzzlemeapp.com Good resources: Apple Documentation, especially the sample projects; http://ericasadun.com/ especially her cookbook; #iphonedev on freenode.net

A common date formatting error is to accidentally use the “iso week year” instead of “calendar year”, which is the same 99% of the time except sometimes at the end of the year, as your example shows. https://ericasadun.com/2018/12/25/iso-8601-yyyy-yyyy-and-why-your-year…

App Store discoverability is getting worse as it is. For the indies, having more channels to get their apps found might not be such a bad thing. https://twitter.com/wilshipley/status/1270568780712706049 https://ericasadun.com/2015/11/11/finding-triviata-on-the-app-store-a-…

If you are a trainer, then having immediate access to all the attendees is fairly important. I'm in the process of "refactoring" my training approach to a videoconference approach (using Zoom). I'm actually really surprised at how intimidating the process has been. I've been doing training and speaking in person for a long time, but not via Zoom. It will work out, but the biggest issue that I'm encountering, is not having access to "immediate feedback." A very good article on the topic was written by a well-known (and extremely effective) trainer, Erica Sadun, here: https://ericasadun.com/2020/03/11/so-youre-going-to-teach-remotely/

unfortunately it is not open source... But they opened sourced Swift Playground Support http://ericasadun.com/2016/07/07/apple-open-sources-swift-playground-s…

Generic typealiases are coming, thank goodness: http://ericasadun.com/2016/03/08/generic-typealiases-are-a-thing/

Another take on guard http://ericasadun.com/2016/01/01/another-take-on-guard/

Output generated from Xcode 6.4 and 7.0: (echo "import Swift"; echo ":print_module Swift") | xcrun swift -deprecated-integrated-repl | open -f http://ericasadun.com/2015/09/01/fetching-stdlib-declarations-in-tcsh-…

People are already blogging mostly in Swift rather than Objective C, which was created in the mid 1980's. http://www.h4labs.com/dev/ios/swift.html Apple is doing a good job of updating ObjC but Swift already has the momentum. Apple has made it clear that they want Swift: http://ericasadun.com/2015/04/14/swift-in-case-you-didnt-think-that-sw… You can choose to ignore their subtle messages (e.g. use Autolayout, Size Classes) but at some point in the not too distant future, you'll likely regret not starting with Swift earlier.

AirPlayer from Erica Sadun would work: http://ericasadun.com/ftp/AirPlay/ However, she mentions that you can't stream music to AirPlayer due to RAOP: http://en.wikipedia.org/wiki/Remote_Audio_Output_Protocol which, I guess is not true anymore due to the parent link :) But it does seem to show that iTunes was indeed checking keys before sending to an Airport Express, but that AirPlay (for video) wasn't affected. As far as I know, AirPlay is not much more than HTTP Live Streaming. Also of interest in the same area (though this is an iOS app, so could technically include some key checking without knowing it): https://github.com/nto/AirView

Video is seemingly not encrypted, only pure audio streams required the key. See Airplayer (http://ericasadun.com/ftp/AirPlay/) and apparently Airfoil Video Player (http://www.rogueamoeba.com/airfoil/mac/) for example.

Certainly a problem they're aware of, and they're trying to get as many breaking changes done in 3.0 as possible. There may or may not be more in 4.0, but they will definitely be smaller. > What does this mean looking forward? Well, Swift 2 to Swift 3 is going to be an unavoidably disruptive change for code since Cocoa renamification is going to land, and we’re going to be building impressive migration technology again. As such, we should try to get the “rearrange all the deckchairs” changes into Swift 3 if possible, to make Swift 3 to 4 as smooth as possible. While our community has generally been very kind and understanding about Swift evolving under their feet, we cannot keep doing this for long. While I don’t think we’ll want to guarantee 100% source compatibility from Swift 3 to Swift 4, I’m hopefully that it will be much simpler than the upgrade to Swift 2 was or Swift 3 will be. http://ericasadun.com/2016/02/29/getting-ready-for-swift-to-stop-break…