That said, I'm always amazed how much discussion that goes into the
topic of memory management in Cocoa / ObjC. My opinion is that the
current scheme works really well, and that someone who works with
Cocoa / ObjC for a living quickly stops thinking about memory
management, because once you learn the basic rules and patterns, it
just works. I don't claim that we never spend time tracking down
memory related bugs / performance problems in our applications, but I
do think that they are a pretty small part of what we have to do.
Right, but you're the fluent Cocoa / ObjC developer. If you want the
language to survive don't you want to entice as many people to become
fluent. All other mainstream programing languages which are being
taught at schools, either have explicit or AGC memory management,
people have to learn the cocoa patterns of reference counting on their
own. Its one of the many barriers that you have to get by to convince
linux programers that have already migrated to macs that they should be
using Obj-C cocoa.
I like the fact that ObjC is a very thin wrapper around C, it's a very
pragmatic approach that works really well. I really like reference
counting, because it seems to strike a nice balance between automation
on one hand, and programmer control on the other. I'm a bit sceptic to
the idea of adding GC to Cocoa / ObjC, but that's probably because I
don't know enough about it. Perhaps it can be done in an efficient and
reasonably non-disruptive way. Dietmar seems to think so, and he
certainly seems to know a lot about GC.
The works fine for you, that works for me, at the moment, but
ObjC/Cocoa is really starting to look very aged. Although I don't think
that not having AGC is the big thing that is making objective-c look
very aged, as that would certainly be the lack of namespaces, but it's
a part of it.
Do not post admin requests to the list. They will be ignored.
Objc-language mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden