1 min read

Issue #32

Hi there!

Hope you're doing good and working toward your goals, whatever they are (whether that's work, resting more, spending more time with family, or protecting what's yours).

Today I have a couple of longer sections - hope you enjoy the read, and I'm always curious to hear your thoughts!

Let's dive in 👇👇

Is it SwiftUI's fault?

In the last couple of months there's been a lot of discourse on Twitter about the betas and the first public versions iOS 16/macOS 13. Some blame the rawness of the first versions specifically on SwiftUI and its immaturity, and this gets reverberated by others. Is it correct or even fair to blame incompleteness of features or bugs on one framework, disregarding other context such as processes, quality of QA, or time constraints?

I won't share the negative takes not to point fingers (I also don't have that many fingers 😂). Here's a few other takes on this, with a bonus positivity thread in the end. Tell me what you think!

Swift 5.7 is here!

If you've already upgraded to Xcode 14, that means you can take advantage of improvements in Swift 5.7.

I might cover more individual features in the future, but in the meantime you can check out the official overview and the full list of evolution proposals released in 5.7.

Here's a thread about improvements to generics and protocols:

On the practical side of things, here's a regex to replace all if let x = x { with the new shorthand if let x {:

Compiler errors ftw

Truth. Linters are also nice :)

Directory of Apple frameworks

A full directory of all Apple frameworks with ability to filter by platform and minimal supported version 💪


Alright, that’s it for today.

Did you enjoy this issue? Let me know by pressing the buttons below. If you enjoyed it, you can help grow the newsletter by spreading the word ☺️

Also I’d love to hear from you. Just reply to this email or DM at @ios_code_review 👋