“And SwiftUI now includes ViewThatFits, which lets you specify multiple variations of a given view and lets SwiftUI automatically choose the one that best fits in the available space.”.

Swift Async avoids many pre-existing terms like "thread", "queue", or "concurrent" so understanding the details of this table is critical. It's easy to end up with everything unstructured on the main actor when you wanted cancellable background work. From

Final note: don't choose RAM over faster CPU. I also tested a 2018 6x2.9Ghz 32GB MBP. Those numbers look better than a 2019 2.6Ghz 16GB MBP but the CPU is 30% slower – not a gap that its bigger RAM will ever close.

These tests were run on 2019 MacBook Pros. Is it different on M1 Macs? I don't have two to compare but RAM numbers will likely be about the same. Performance difference may be less noticeable but I'd expect similar ratios between 16GB and 32GB machines.

Do you need 32GB for iOS dev? No, but memory up to 32GB is rarely *wasted* when IDEs are involved, even the difference is subtle. Of course, it's still completely viable to build iOS apps on a 2017 MacBook Air with 8GB of RAM, if that's all you have. Slower but functional.

Without a stopwatch, I can't tell the two apart – both systems have been equally responsive. But now I'll add a Parallels Windows VM in the background. An easy 30% performance win to the 32GB machine. Worse: the 16GB machine noticeably stalls when swapping between apps.

Simulator + SwiftUI previews and all the RAM on a 32GB machine is used. Now, the 32GB machine beats the 16GB one by 10% or more. Don't be too worried if you can afford only 16GB since the difference is never more than 25%, even with a standard spread of apps in the background.

Everything takes different amounts of RAM based on the total RAM of the system. My 16GB system running Xcode shows 8GB "Memory Used" in Activity Monitor but the 32GB system shows 12GB. (The Xcode process shows just 586MB used, the rest spread around 822 other processes.).

Xcode alone can fill the RAM on a 16GB system. Yeah, okay, half of that is "Cached Files" (not app memory) so the effect is subtle. Incremental builds are 5% slower compared to a 32GB system but clean builds are about the same. (Blue is 16GB, green is 32GB, lower is faster.)

Instead, I spin the Wheel of Autocomplete and nearly a third of the time I get useful options but mostly, I get documentation that tells me what I’ve already typed, or technically correct but useless autocomplete for `Optional`.

If Xcode’s autocomplete popup for `font` would show the “Dynamic Type Sizes” table from Human Interface Guidelines, it would save me many hours per year.

Building | 10 / 100 👀.Building | 90 / 100 👀.Building | 100 / 100 🙂.Building | 120 / 210 🤨.Building | 125 / 1920 🤬. I would trade a few seconds of build time for Xcode's progress maximum to be better estimated (or retained between runs).

RT @SwiftLang: Announcing Swift Async Algorithms, a new open source package providing asynchronous functions for zip(), merge(), debounce()….

> Apple confirmed to Ars that the 27-inch iMac has reached end of life. I’ve owned 2, over the years. Both times I would have preferred a cheaper, up-to-date Mac Pro, so I guess this is good? Still a little shocking to see it just disappear.

Some fascinating analysis of the programming languages used in iOS 15 by @timacfr. The smooth exponential growth of binaries looks like apps are reproducing in the wild 🙃.

It takes more than 2 hours after downloading Xcode to install via App Store. installd peaks at 3 cores but uses 1 core most of that time. How is this not streamed, parallelised and faster than the download? A better design here would save literally millions of hours, per release.

Weirdest macOS Monterey bug. when I play games through my Bose QC35II bluetooth headphones, the audio for the entire system (not just the game) drops a 6th in pitch. Everyone sounds like monsters – even in videos playing in another app. It's terrifying.

RT @johnsundell: To celebrate the 100th episode of the Swift by Sundell podcast, I’m really excited to have @clattner_llvm back on the show….