If developers should transition to 64-bit (as Greg says they should), then:
* The docs are outdated and misleading. * This is bad for developers who assume the docs are up-to-date and reliable. * Right or wrong, some developers will fall into this category. * It behooves Apple to update the docs, for the sake of those developers. It seems to me Jayson agrees with all the above, while making a point of not commenting on his own work or making predictions about the future of 32-bit. Differences of opinion seem to be in the following areas. * If Developer X blindly believes the docs and doesn't check the cocoa-dev archives, do they deserve what they get? * If Developer Y is aware of this issue, are they morally obliged to file a Radar and/or documentation feedback? I am not offering an answer to either of these questions, but for the record, because of this thread, I submitted documentation feedback at the link posted earlier. For those who've never done this, it's *much* easier than a Radar (though I don't know if it has the same impact on priorities at Apple). See the feedback links at the bottom of the page: <https://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/64bitPorting/indications/indications.html#//apple_ref/doc/uid/TP40001064-CH206-TPXREF101> > Please update this document to flatly recommend transitioning apps to 64-bit. > Many of the caveats are no longer applicable. > > See http://lists.apple.com/archives/cocoa-dev/2012/Aug/msg00330.html. Here's what it looked like before I hit Submit: <http://imgur.com/3hJW5>. --Andy _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
