There's a weird niche feature of Swift that lets you use didSet on local variables. I found that you can use it to hide implementation details when calling Closure blocks similar to those you would use for a Domain-Specific Language.
Everybody’s talking about the Apple Watch around the anniversary of its first release. Most of the chatter is about how [disappointing and how slow it is](https://sixcolors.com/post/2016/02/why-slowness-is-killing-the-apple-watch/), with some countering with [how useful it is despite this](https://www.caseyliss.com/2016/4/11/poor-apple-watch). I am in agreement with most of these viewpoints, but people who don’t think this is going to change radically in the next year or two are crazy. You only have to look at the utility gulf between a first-generation iPhone and the iPhone 4 to see this.
We're having a WWDC Keynote party in England, with free ? + ?.
Since the improvements to Touch ID you see many people complaining that they press the Home button to see the lock screen to catch some missed push notification or check the time, and it instead unlocks the phone. The new Apple TV remote has a nice feature where the Apple TV itself dims the display when inactive, and “wakes” up brighter when you lift the remote. Obviously this is using the accelerometers in the remote. […]
The pace of change, the reliable yearly cycles, they are hard to keep up with. However I just can’t deny that iOS dev is also consistently exciting. You know there’s cool new stuff coming all the time and a world of interesting possibilities that can affect a huge number of people in the world.