What I see developers get frustrated with, is the fact that frameworks (or other technologies) get released with great hype, wind up being half baked... and then instead of that thing ever being improved, it's onto the next greatest hype.
The judgement calls seem particularly odd at times, especially when it comes to graphics. I would even go so far as to say that it seems that there has been great confusion, considering the output.
I think Apple would do well to consider what has really improved since 10.5 and what has not. It's never too late to turn back from bad directions.
-gt
On Aug 27, 2015, at 1:56 PM, Jens Alfke < email@hidden> wrote: On Aug 27, 2015, at 9:46 AM, Thomas Wetmore < email@hidden> wrote:
I have also been disappointed on how much difficulty I have had when incorporating new Apple technologies.
In the case of Swift, I think it’s mostly just that it’s new (and still developing fast) and quite different from what we’re used to. Apple has done a great job documenting it — I remember being blown away at WWDC last year by how good the Swift books were.
In some other areas, like auto-layout, Apple’s made adoption harder than it needs to be by not documenting it well, or by hiding the documentation (in a sub-basement behind a door reading “Beware Of The Leopard”.) The Xcode IDE documentation is wretched, I might even say “insulting”; super-complex things like build settings are given one page with a screenshot and some superficial one-liners about what the buttons do. Similarly-complex GUI tools in other domains like audio or illustration get big tomes of documentation, but the Xcode IDE (I’m not talking about the SDKs!) has basically a pamphlet.
—Jens
|