3 ms·

Engineering is not organized by platform, but function. Apps that are cross-platform have engineers who move back and forth between macOS and iOS. Lots of code

Engineering is not organized by platform, but function. Apps that are cross-platform have engineers who move back and forth between macOS and iOS. Lots of code is also reused between the two. Both platforms use essentially the same tooling and languages (if anything, iOS development is more painful), though certainly iOS codebases tend to be better because they are newer. A fight for attention by a specific, resource-starved macOS engineering team could not be more incorrect. That’s simply not how Apple works. You have to come up with a different explanation for these perceived quality problems.

bangonkeyboard 7y ago
> You have to come up with a different explanation for these perceived quality problems. The developmental move to agile deadline-driven feature-sprints under Craig Federighi.
skywhopper 7y ago
Well, customizable menu-based keyboard shortcut support is not a cross-platform feature. So maybe there's no one responsible for it? Which amounts to a management/resource-allocation problem as suggested above. The team organization you describe would contribute to the problem of this sort of Mac-specific thing being marginalized and de-prioritized, exactly as described above.
- shuckles 7y ago
  No. There is no fight for recognition or status of the kind the parent extrapolates. “Resource allocation problem” is general enough that it could explain basically every bug, so that’s not particularly helpful. The way to think about this is that the menu bindings are AppKit features which share resources with UIKit. An interesting theory would be one which identifies (i) who in the organization gets to gate what ships and decides it’s good enough (ii) what are their incentives. At a company like Apple which is huge, has marketing deadlines, and is coordinating hardware, software, and services releases, both items have very subtle and interesting answers.

bangonkeyboard 7y ago

> You have to come up with a different explanation for these perceived quality problems. The developmental move to agile deadline-driven feature-sprints under Craig Federighi.

skywhopper 7y ago

Well, customizable menu-based keyboard shortcut support is not a cross-platform feature. So maybe there's no one responsible for it? Which amounts to a management/resource-allocation problem as suggested above. The team organization you describe would contribute to the problem of this sort of Mac-specific thing being marginalized and de-prioritized, exactly as described above.

shuckles 7y ago
No. There is no fight for recognition or status of the kind the parent extrapolates. “Resource allocation problem” is general enough that it could explain basically every bug, so that’s not particularly helpful. The way to think about this is that the menu bindings are AppKit features which share resources with UIKit. An interesting theory would be one which identifies (i) who in the organization gets to gate what ships and decides it’s good enough (ii) what are their incentives. At a company like Apple which is huge, has marketing deadlines, and is coordinating hardware, software, and services releases, both items have very subtle and interesting answers.