16: John, We Don't Play Games

Legacy API Issues

Apple's legacy APIs present significant challenges for developers, particularly when dealing with outdated systems like Objective-C. Marco Arment highlights the difficulties of managing memory with these older APIs, which often lack modern conveniences like Cocoa wrappers 1. This results in developers having to navigate complex, low-level code, leading to potential security and performance issues. John Siracusa adds that the reluctance to update these APIs stems from organizational inertia, where teams are resistant to change due to established practices 2.

It's stupid. It would take them not very long, not that much effort, not any kind of significant long-term maintenance cost just to make really basic wrappers around these things.

--- Marco Arment

This resistance to modernization is a source of frustration for many developers who seek more efficient and secure coding practices.

   

Modernization Needs

The need for modernizing Mac development tools is evident as developers face challenges aligning them with modern iOS tools. Casey Liss and Marco discuss how outdated Mac APIs hinder development, despite the availability of powerful hardware 3. They suggest that integrating modern features from iOS, like UIKit conveniences, could enhance Mac development efficiency. John Siracusa notes that while some modernization efforts have been made, such as block support, legacy issues still persist, affecting the overall development experience 4.

There's just like legacy hanging around. When I see stuff like that, I think, well, it makes me think about the Mac as a platform overall.

--- John Siracusa

The conversation underscores the importance of updating Mac APIs to attract more developers and improve productivity.