Of the choices that he proposes, #2 seems like the obvious solution to me - but he writes it off as too difficult.
Phabricator’s stacked diffs [0] works wonderfully well to support this exact workflow (it isn’t clear from the post which versioning system the author uses and what workflows it supports - maybe I missed it?)
The minute I saw "Apple" and "reality distortion field" and "propaganda" in the same sentence was the minute that I knew this comment was full of shit.
Edit: didn't mean to sound snarky, but it's really terrible to trash an entire article based on a single sentence.
>> How exactly is putting a little scanner inside a button going to be meaningfully better?
Quoting from the article:
"Apple's Touch ID was the biggest surprise for me. I found it very well executed and a nice part of the overall experience. When between the 5s and the 5/5c, I immediately miss Touch ID."
Coming from someone as respectable as Anand, I would call that reasonable grounds to call TouchID "meaningfully better".
Maybe you can point to something similar for face unlock?
>> What's the infatuation with performance in a cell phone?
Assuming you're talking about GPU performance: Apple cares a lot about GPU performance because iOS uses the GPU heavily for a lot of tasks - all the animations, transitions, blurring and blending effects that you see are executed on the GPU, mostly via CoreAnimation.
Also, there are new games and other applications that are pushing GPU requirements to near desktop-class. For example, the Infinity Blade demo that was shown during the launch.
I think a lot of people care about having enough GPU performance to enable all of these.
> Apple was unwilling to negotiate with Google because they are upset over Android. Apple could certainly have improved its existing Maps app if they were willing to play ball with Google.
You speak like you have authoritative information on the negotiations between Apple and Google on maps. Your comment could be taken seriously if you backed it up with sources, instead of dressing up your personal opinion to sound like a fact.
Phabricator’s stacked diffs [0] works wonderfully well to support this exact workflow (it isn’t clear from the post which versioning system the author uses and what workflows it supports - maybe I missed it?)
[0] https://jg.gg/2018/09/29/stacked-diffs-versus-pull-requests/