5 ms·

> me neither. yeah Objective-C is not memory safe but no seasoned programmer would ever make those mistakes that Swift aims to solve here - with a high price.

• dinkblam 3y ago
  have you ever had a look at any Objective-C codebase? Objective-C is a high-level language and there usually is no memory manipulation. just because the possibility exists (via dropping down to the C part of it) doesn't mean it is done. ARC does memory management for you and there hasn't been the need for manual memory management in ages. even that was pretty hassle-free. i can count the memory bugs i have seen our Objective-C projects in the past 10 years on one hand. > entire history of memory safety related bugs and security issues you are talking about C and C++, not Obj-C
  • pjmlp 3y ago
    One just needs to read Apple's security bulletins to know how it actually works in practice.
• b3morales 3y ago
  A citation is needed for the number of iOS projects that have more than a minuscule amount of code at the application level that risks memory unsafety.¹ The value proposition becomes stronger for the system frameworks that the app consumes, of course. (Although even the stdlib dips more than once into memory-unsafe Swift for performance.) But this brings us to another of the points from the article: is it really best to use one language for both use cases? ¹And additionally for whether those project would eliminate such code if rewritten in Swift.
  • pjmlp 3y ago
    Apple's security bulletins for one.