This is the tenth post in the Advent of Technical Writing series, wherein I will share something I have learned from my experience as a technical writer. My experience is primarily in software technical writing, but what you read may apply to different fields, too. View all posts in the series.
I wish Apple followed these rules. So many deprecations in their man pages and developer documentation have no details at all. No idea what the supposed replacement is. No idea of the underlying reasons. No idea when it will cease to function.
This is why I still see “launchctl load” everywhere. It’s been deprecated for years, but the replacements are overcomplicated and not clearly communicated in official docs. When Apple finally pulls the plug, so much shit out there is going to break.
When they deprecated python2, they withheld implementation details and any timeline. Then they finally axed it in a freaking minor point release, without even replacing it with python3. AAAAAAH
I wish Apple followed these rules. So many deprecations in their man pages and developer documentation have no details at all. No idea what the supposed replacement is. No idea of the underlying reasons. No idea when it will cease to function.
This is why I still see “launchctl load” everywhere. It’s been deprecated for years, but the replacements are overcomplicated and not clearly communicated in official docs. When Apple finally pulls the plug, so much shit out there is going to break.
When they deprecated python2, they withheld implementation details and any timeline. Then they finally axed it in a freaking minor point release, without even replacing it with python3. AAAAAAH