Sponsored Link
The Swift Algorithms Book (30% off)
Written for students and professionals, The Swift Algorithms Book blends modern code, illustrations and computer science to help you pass the interview or build your next app. Perfect for the classroom or the office, the book takes a fresh approach to explain concepts that power search engines, databases and social networks. Use code coupon code "IOSDEV" at checkout to receive a 30% discount!
News
The Talk Show - Interview with Craig Federighi
This week's episode of The Talk Show started with Craig Federighi talking about the Swift open source release. There wasn't much new information revealed but it was nice to hear it in Craig's words and it was an relaxed, enjoyable conversation. There's also a transcript if you'd prefer to read rather than listen.
Accepted!
Just two weeks in and already the first Swift Evolution proposal from the community has been accepted. Erica Sadun proposed the removal of C style for loops from the language, and it's been accepted! They will become a warning in 2.2 and an error in 3.0. I like the proposal, but I'm really happy to see how the discussion and acceptance process on the mailing list was treated in exactly the same way as the proposals from within Apple. The same mailing list is also the source of some little gems of information like this post on dynamism in Swift by Chris Lattner. It's very exciting to see all of this happen in public.
Tools
If you're writing Swift, it's a fairly safe bet to assume you're writing it in Xcode, or possibly AppCode. But there were a couple of projects that caught my eye this week which could mean that your choices for editors/IDEs might expand over the next few months.
Hacking Atom to create a Swift IDE
First up is this experiment from Ankit Agarwal. He's integrated the LLDB debugger with Atom. It's very rough and ready (naturally) but it shows promise. You're not going to be writing iOS apps with Atom any time soon, but maybe something server side? Interesting article anyway.
SourceKittenDaemon
This project is also worth checking out. Benedikt Terhechte has put together a daemon which interacts with JP Simard's SourceKitten framework (which I also hadn't come across!) to expose Swift autocompletion as a service. There's a demo of it being used in a simple editor but naturally this could be used anywhere.
swiftenv
Oh and if you're experimenting with the various unreleased versions of Swift, this tool by Kyle Fuller will come in handy for switching your environment.
Code
A Structy Model Layer
Soroush Khanlou on the choice between classes and structs for model objects. I recently experimented with building some models using structs and while it was an interesting exercise, ultimately it it ended up being a significantly more complex solution and didn't feel right. This article is a good summary of where it works and where it's not a great choice.
When (not) to use guard
I love guard
, it makes code so much simpler and was a great addition to the Swift language. Are you overusing it though? Or underusing it? It's a subtle topic, but very well explained here by Radek Pietruszewski.
Details matter - Harnessing the power of CoreAnimation
Krzysztof Zabłocki with a great tutorial on reproducing the animations and interactions from the Stripe Checkout. There's not really any new techniques here but it's good to see it all put together.
Awesome Swift Education
An extremely comprehensive list of everything you could possibly want to know about Swift. Blogs, books, quick references, presentations, videos, and a whole load of specific, categorised blog posts.
Videos
Functional Swift Conference 2015 - Videos
This conference only happened a week ago and already the videos are available! This alone is proof that functional programming is best. 😄
Sponsored Jobs
iOS Engineer (Karma; New York, NY)
Empowering people with internet connectivity, everywhere they go.
And finally...
Fallout 4 Service Discovery and Relay
Fascinating investigation of how the Fallout 4 companion app communicates with the PlayStation 4.
Comment
There's been plenty of talk recently about the App Store and to be honest I've been avoiding linking to it. Not particularly because it was primarily focused on the Mac App Store, but because the majority of it had been said before, and there really were no signs that anything would change.
However, yesterday saw the announcement of Phil Schiller being given responsibility for the App Stores. The App Review team was already under his control as part of developer relations, but moving everything under one roof feels like an opportunity for some changes. New leadership is surely going to prompt a thorough look at how Apple sees the App Stores functioning and that can only be a good thing. I also agree with Rene Ritchie who would like to see someone have the App Stores as their primary responsibility, reporting to Schiller.
I wouldn't hold your breath for quick changes, but fingers crossed that this is the first step towards a brighter App Store future.
Dave Verwer