There’s an article in TidBITS I really enjoyed: Six Reasons Why iOS 13 and Catalina Are So Buggy. Unfortunately, while the actual points in the article are great, both the headline and introduction are… sensationalist. It’s a list with a headline designed to grab your intention.
This year I worked on a Core Data application. All of the parts of its sync were in a single file, which as a result had too much state tracking. The result wasn’t just complicated, it was dangerous. Should a state change be missed, the operation would never complete.
Recently, CBC posted Still don’t own a smartwatch? You’re not alone. First, let me say I agree with the author that not everyone needs or wants a smartwatch. I certainly don’t need one, but did want one. I got an Apple Watch as an early birthday present last September or October. And I really do enjoy it.
Recently, a number of reporters have put on their very best nostalgic glasses to look at the history of Apple software. Walt Mossberg: In the last couple of years, however, I’ve noticed a gradual degradation in the quality and reliability of Apple’s core apps, on both the mobile iOS operating system and its Mac OS […]
In the past if you wanted to include data in your command line app, you could either include it in a separate file or do some linker trickery to embed it. Personally, I never really got into the linker trickery (though it’s probably the better solution of the two). For a while, though, Xcode has […]
Do you have an app where the row heights in a table view shift, especially when navigating away from a view controller? This seems to be an iOS bug and is caused by using autolayout within a table cell without a tableView:estimatedHeightForRowAtIndexPath: method.
You know what I really hate? Defending Facebook. CBC has a story right now on how Facebook Messanger captures more data than you think. And thanks to how inaccurate that story is, now I have to defend Facebook. Way to make my day, CBC.
Jon Friskics suggets Swift is great, but you should still know Objective-C first. Dave Mark agrees. Let me give you a different opinion: No, newbie, you don’t need to learn Objective-C first. You’ll miss it from time to time and you might want to pick it up later, but it won’t help you much now. […]
I’ve had some recent troubles trying to upload a build in Xcode. These involved getting a really unhelpful error from Xcode: “No identities were available.” Unfortunately, I was stuck there for two days. It turns out that you can get Xcode to log more information on the handshake with the portal. Quit Xcode, then run […]
NSIndexPath is easier to use than you might think. If you read the documentation for the class, you’ll see this: