Archive for December 13, 2019

Friday, December 13, 2019

UserDefaults Access via Property Wrappers

Christian Tietze:

The hip and cool property-wrapper implementations on the web so far ignore the registerDefaults layer completely and provide a local fallback if no value for the key is persisted for the current user.

The problem I see here is that you don’t have a shared default value anymore. Knowledge of the default value is local to the property declaration in a concrete type.

A full solution would include something like:

  1. A pair type that combines a key with a default value.
  2. A connection between that and UserDefaults for getting and setting values.
  3. A way to access predefined pairs from different places in your code.
  4. A full list of the predefined pairs so that they can be registered.
  5. A way to link a property to a pair and a given instance of UserDefaults.

SwiftUI Deal-Breakers

Weston Hanners:

SwiftUI is really fun and the data flow is just awesome. It makes building new screens super quick and opens the door to a ton of prototyping.

I am sure these will all be fixed in time, but many of these are deal-breakers and as it is right now, I will not recommend SwiftUI for any paid projects I am involved with.

His post is about iOS. More stuff is missing for macOS.


Google Achieves Its Goal of Erasing the WWW Subdomain From Chrome

Lawrence Abrams (Hacker News):

With the release of Chrome 79, Google completes its goal of erasing www from the browser by no longer allowing Chrome users to automatically show the www trivial subdomain in the address bar.


Many users, though, felt that this was a security issue, could be confusing for users, and is technically incorrect because is not always the same host as


Update (2019-12-16): Tanner Bennett:

This seems like their most controversial change since they tried to pull that stuff with adblockers not too long ago.

“” displays as “”.

Completely wrong.

A. Lee Bennett Jr.:

I have literally seen corporate web sites that only worked if www. was in front. It 503’d if the subdomain was missing.

Pro Display XDR Limited to 5K With iMac Pro

Joe Rossignol:

Thomas Grove Carter has since demonstrated that the iMac Pro can in fact drive the Pro Display XDR, but only at a 5K resolution. This is likely because the iMac Pro uses Intel’s older “Alpine Ridge” Thunderbolt 3 controller without enough bandwidth to drive a 6K display.


To use the Pro Display XDR at its full 6K resolution, the display must be connected to the new Mac Pro with MPX Module GPUs, a 2018 or later 15-inch MacBook Pro, a 16-inch MacBook Pro, or a 2019 iMac.

This makes sense given that the iMac Pro’s specs haven’t been updated since it was announced in June 2017. Hopefully that will change soon.