On Aug 22, 2008, at 7:54 AM, Joeles Baker wrote:
Just read through the book.I really wonder, what the author of the foreword (obviously an apple employee) thought, when Mac OS X was announced :-)Is this really true? Is Unix "defective by design" ? :-)
Amazingly powerful tool, easy to remove a limb. Kind of like the Hole Hawg:
http://www.team.net/mjb/hawg.htmlWhich is why, when I write Cocoa programs, I stick to the highest level APIs as much as possible; Cocoa, CoreData, Foundation, CoreAnimation, etc...
It makes my code easier to maintain and, more attractively, it means that my code just naturally gets faster and has more features as Apple adds stuff to the system and optimizes existing stuff. Look at the performance gains in CoreData between Tiger and Leopard, for example.
Yet, I can still dip to Unix or other underlying "at the metal" APIs when I need to solve a particular performance problem or have access to a feature in a specific configuration that Cocoa has not yet encapsulated.
Write the Code. Make it Work. Make it Right. Make it Fast.To bring this back around to the OP's question, passing user passwords on the command line is *never* the right answer. Which is why Mac OS X provides authentication/authorization APIs (and extensive documentation).
Vladimir: Why are you passing the password as an argument? b.bum
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
