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…
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…
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…
Probably not, but there's not much point in doing so, as you'll pee it all out anyway.
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…
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…
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…
Probably not, but there's not much point in doing so, as you'll pee it all out anyway.