Annoyances of API Design
<p><pre><code>    outputImageProviderFromBufferWithPixelFormat:pixelsWide:pixelsHigh:baseAddress:bytesPerRow:releaseCallback:releaseContext:colorSpace:shouldColorMatch:
</code></pre>
No, this is <i>great</i>! I can glance at something calling this, and, without any comments, determine immediately what each parameter is!<p>Note that standard formatting is to place each argument on its own line, with the colons lined up, and that Xcode does this automatically, and will autocomplete the entire nonsense. It's fairly disingenuous to line the whole thing up as if you need to type it all out.<p>Also, this is an API that clearly bridges to C-style data structures. Higher level APIs will have much fewer parameters.<p>> What’s the difference between a tap and a touch?<p>In Apple-land, at least, a <i>tap</i> is an action (touching somewhere and releasing quickly, as opposed to a swipe, etc.), and a <i>touch</i> is where a user's finger is currently placed.