rhysmorgan

Could not agree more. Users don't need to be "fooled" by an uncanny-valley, years-out-of-date looking simulacrum of native UI, because they're getting the real deal. Accessibility is so overlooked, while some native UI toolkits provide at least a passable default accessibility implementation.

You can totally get 4K 60Hz, so long as the USB-C port supports DisplayPort 1.4a Alt-Mode.

(which raises one of the problems with USB-C - it's impossible to tell how what features it supports)

> I'm going to find him something simpler to work on.

Sure, but why should this non-feature which makes code harder to read and reason about even be built in the first place? All to save `.parse` at the call site of a parser, for example?

Why is it all about succinctness? Swift has never been about succinctness - it’s always been about clarity, without over-verbosity. Sometimes, it just takes a decent number of characters to describe something. That’s not necessarily a flaw, especially if it makes something easier to read.

Seeing .copy() makes it much clearer to understand that what I’m receiving is a copy of something.

If you want a Button template, either extend Button with a method taking the parameters you want, or write a curried free function or something. callAsFunction adds absolutely nothing to the language, bar confusion at the call site.

Probably not, but there's not much point in doing so, as you'll pee it all out anyway.