NYTimes Objective-C Style Guide
A deprecated Objective-C style guide outlining coding conventions used by The New York Times iOS teams.
What is NYTimes Objective-C Style Guide?
The NYTimes Objective-C Style Guide was a detailed style guide for Objective-C programming, created by The New York Times iOS teams. It provided conventions for writing consistent, readable, and maintainable Objective-C code, covering syntax, naming, formatting, and best practices. The guide aimed to standardize code across teams to improve collaboration and reduce errors.
iOS developers and teams working with Objective-C, particularly those seeking to adopt or reference established coding standards from a large-scale organization.
It offered a well-documented, organization-tested set of rules that aligned with Apple's guidelines while adding specific, practical conventions. Developers could use it to ensure code consistency and quality, especially in team settings where uniform style is critical.
Overview
The Objective-C Style Guide used by The New York Times
Use Cases
Best For
- Teams adopting a unified Objective-C coding standard
- Reference for Objective-C best practices and conventions
- Learning organization-specific style guidelines for iOS development
- Maintaining legacy Objective-C codebases with consistent formatting
- Comparing different Objective-C style guides (e.g., Google, GitHub)
- Understanding deprecated but historically significant iOS team standards
Not Ideal For
- Teams building new iOS applications primarily in Swift or using modern frameworks
- Projects requiring actively maintained style guides with updates for latest iOS features
- Developers seeking lightweight, flexible coding standards for small, solo Objective-C projects
Pros & Cons
Pros
The guide covers a wide range of topics from dot notation to error handling, providing detailed, enforceable rules for consistent Objective-C code.
Tailored for large teams at The New York Times, it includes strict formatting and naming rules to ensure readability and maintainability in collaborative environments.
It references Apple's documentation and adheres to their coding guidelines, making it a reliable standard for Objective-C development aligned with best practices.
Each guideline is accompanied by code snippets showing correct and incorrect usage, aiding in quick understanding and implementation.
Cons
Marked as deprecated with no further development, so it lacks updates for newer Objective-C features or iOS versions, potentially including outdated practices.
Focused solely on Objective-C, it's irrelevant for Swift or mixed-language projects, limiting its utility in modern iOS development where Swift dominates.
Strict conventions like mandatory braces for all conditionals and four-space indentation might be unnecessarily cumbersome for simple or experimental code.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.