4 ms·
Some of us happen to think that no GC is a good thing, in Obj-C's case. Swift eschews it as well.
by readymade 10y ago
Some of us happen to think that no GC is a good thing, in Obj-C's case. Swift eschews it as well.
- qwertyuiop924 10y agoManual memory management: It's all fun and games until OOM errors come knocking, or- Segmentation Fault: Core Dumped. I rest my case. There's a place for manual memory management. It's not in application code.
- pzh 10y agoNot necessarily. Swift uses ARC by default, and you'd really have to go out of your way to do any manual memory management.
- qwertyuiop924 10y agoAh. I originally talking about Objective-C, so I assumed that we were talking about manual memory management. Of course, ARC has its own problems... Hope anybody implementing graphs knows what they're doing, or you'll leak memory like Niagra Falls.
- readymade 10y agoObjective-C also uses ARC by default, and that's been the case for several years now. In any event, avoiding retain cycles is relatively straightforward and most iOS devs I know would agree that the low memory overhead and lack of GC pauses are worth the occasional extra effort of weak references.
- qwertyuiop924 10y agoI didn't know that Objective-C defaulted to ARC. Thanks for the information, and I am sorry for misrepresenting the language.