I linked to several posts from Jeff Watkins on leveraging
UIButton rather than replacing it last month. So is this post more on the same subject? Kind of, but he does run out of steam with UIKit's button class in this post. I do like that he says this though:
There’s still no excuse for using UITapGestureRecognizer to solve this problem.
It's worth a read.
It's always easy to overlook error handling, especially if you're writing blog posts or sample code. For example, The Core Data template code Xcode generates has this to say on the subject. 😂 It's understandable of course, handling errors isn't trivial, and if every sample code project included thorough error reporting, it'd detract from what samples were demonstrating. It did make me very happy to see John Sundell tackle the subject this week though. It's something we should talk about more.
Like Bill Atkins, I too am keen to see Swift get support for
await style concurrency. I did like this article in which he argues that with Combine, Swift already has what Chris proposed. I'd still like to see the language take on this challenge in the future, but before that happens, Combine can help you tame concurrency.
I had heard of EarlGrey before, but I hadn't seen anyone write about it until now. Here's Maksym Shcheglov with a rundown of how its approach differs from
XCUITest and some example tests.