How Apple hides new functionality in iOS: isYoMamaWearsCombatBootsActive

Why? Sometimes functionality has to be exposed, even when a company would prefer an alternative. Microsoft has named functions similarly on occasion [1].

[1] http://blogs.msdn.com/b/oldnewthing/archive/2003/10/15/55296...

Re: How Apple hides new functionality in iOS: isYoMamaWearsCombatBootsActive

#8

Post by [deleted] » Thu, Sep 12, 2013, 7:48 AM UTC

[deleted] wrote: post #4

[deleted]

[deleted]

Re: How Apple hides new functionality in iOS: isYoMamaWearsCombatBootsActive

#9

Post by ultimoo » Thu, Sep 12, 2013, 7:49 AM UTC

I wonder whether Apple will decide to change their strategy of aggressively guarding upcoming products before they are launched, under Cook's leadership.

I was following a couple of 'rumor' blogs prior to the iPhone launches earlier this week and I believe they had managed to 'leak' and publish details on the iPhone 5C and 5S pretty spot on.

EDIT: rather than referring to the variable names in the OP, I'm referring to the more overarching strategy of guarding the features of their to-be-launched products.

Re: How Apple hides new functionality in iOS: isYoMamaWearsCombatBootsActive

#10

Post by chatman » Thu, Sep 12, 2013, 7:51 AM UTC

fruchtose wrote: post #7

[deleted] wrote: post #4

[deleted]

Why? Sometimes functionality has to be exposed, even when a company would prefer an alternative. Microsoft has named functions similarly on occasion [1]. [1] http://blogs.msdn.com/b/oldnewthing/archive/2003/10/15/55296...

Because he might've appreciated better variable naming. :-P