A deprecated Objective-C style guide outlining coding conventions used by The New York Times iOS teams.
NYTimes Objective-C Style Guide is a deprecated set of coding conventions for Objective-C, originally used by The New York Times iOS teams. It provided detailed rules for formatting, naming, and best practices to ensure consistent and maintainable code. The guide aimed to standardize development practices and prevent common pitfalls in Objective-C programming.
iOS developers and teams working with Objective-C, particularly those seeking to adopt or reference established coding standards from a large organization.
Developers chose this guide for its thorough, well-documented conventions that reflected real-world usage at a major publication, offering clarity on nuanced topics like error handling, literals, and thread-safe singletons.
The Objective-C Style Guide used by The New York Times
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The guide meticulously details rules for syntax, formatting, naming, and error handling, with examples like mandating braces in conditionals to prevent common bugs.
Each convention is explained with reasoning, such as using CGGeometry functions for CGRect access to avoid standardization issues, making it educational.
Includes NYTimes-specific practices like three-letter prefixes for constants and thread-safe singleton patterns, ideal for large team consistency.
Explicitly cites Apple's documentation and aligns with Cocoa conventions, providing a solid foundation while adding nuanced guidelines.
Marked as deprecated with no further updates, so it doesn't cover newer Objective-C features or iOS best practices, limiting its relevance.
Strict mandates like 4-space indentation and detailed image naming conventions can be cumbersome for projects not requiring such rigidity.
As a deprecated guide, it offers no integration with current linters, IDEs, or community tools for automated style enforcement.
Some recommendations, such as those around ARC qualifiers or error handling patterns, might be superseded by evolving Apple guidelines.