If I were Supreme Swift Potentate, there are a few things I’d change about how Swift deals with protocols, and how this gets manifest in the standard library.
I subscribe to a couple of mildly interesting and low-volume email lists. One such list is the
tz-announcelist hosted by ICANN. It’s the list for people who care way too much about timezones.
I’ve developed a handy trick when writing frameworks in Swift that makes the overall process a little bit nicer, and it’s just adding a single file to your framework.
When you’re writing an iOS or macOS app, you typically don’t need to dynamically know what your own entitlements are. However, there are a couple of rare circumstances when it could be Nice To Have.
Finding the root cause of an error in your app can often feel very intimidating, whether you’re brand-new to programming or you’ve been building coding for decades. Debugging problems can be extremely time consuming. Where do you start looking? How do you know if what you think is the problem is actually the problem?
Recently I’ve posted a couple of tweets rating some movies I’ve seen, and I almost always get asked about my rating system, because it’s a little unusual.
Part 4 in a series on “fixing” Model-View-Controller:
Part 3 in a series on “fixing” Model-View-Controller:
Part 2 in a series on “fixing” Model-View-Controller: