Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7957405
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T04:14:43+00:00 2026-06-04T04:14:43+00:00

This question aims to understand Objective-C’s manual memory management currently, and its use in

  • 0

This question aims to understand Objective-C’s manual memory management currently, and its use in the past.

It is said that people who worked with Objective-C for many years almost treat memory management in Objective-C like a “reflex”… (the alloc, retain, release, autorelease)

But isn’t it true that if Objective-C is used on a computer, then there is garbage collection? Isn’t it true that manual management in Objective-C isn’t needed until the recent use of it on iPhone and iPad because iOS has no garbage collection? How about in the past, maybe back in the 90s, when Objective-C has no garbage collection, or does it always have garbage collection but since the iPhone came out, then the retain and release were added to the language?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-04T04:14:43+00:00Added an answer on June 4, 2026 at 4:14 am

    To answer the question you actually asked, Objective-C only gained garbage collection with the release of Mac OS X 10.5 Leopard in (late) 2007. Prior to that, manual memory management was the only option. Even after the release of Leopard, most Cocoa developers didn’t use garbage collection for various reasons: inertia of existing codebases, need to support older OS versions, performance penalties inherent in using garbage collection, not supported on iOS, etc.

    ARC has been adopted more quickly for several reasons, and I (and obviously Apple) think it’s a much better solution than garbage collection. ARC was made available with the release of iOS 5.0 and Mac OS X 10.7 Lion (with partial support for deploying to iOS 4.3 and Mac OS X 10.6). Lion and iOS 5 were both released less than a year ago, so any developers who have been writing Objective-C longer than that use/used manual reference counting, and you’re correct that it’s reflexive for most of us.

    While ARC has been adopted quickly, at least compared to garbage collection, its use is still far from universal. Anyone needing to support iOS 4.2 or earlier or Mac OS X 10.5 or earlier still absolutely has to use manual reference counting. Also, I think there are a lot of seasoned Cocoa programmers who simply haven’t seen a reason to switch to ARC yet, since for them, manual reference counting isn’t a huge burden.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

This question aims to understand RoR and frameworks in general. It looks like RoR
This question is about tidying up code and better management of said code butI'm
I use example with Rails 3, but I believe that this is true for
This question might look naive, but I couldn't understand this code in the ViewModelLocator.cs
This question is not strictly related to Symfony 2, but as I use Symfony
I ask this question to determine which memory allocation algorithm gives better results with
This question has been retitled/retagged so that others may more easily find the solution
This question is related to that one. But somewhat extended. Let's assume we have
This question concerns converting a floating point number that is less than abs(1) and
This question is a little subjective, however, it aims to give me a bit

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.