Re: Cocoa et al as HCI usability problem
Re: Cocoa et al as HCI usability problem
- Subject: Re: Cocoa et al as HCI usability problem
- From: Alex Kac <email@hidden>
- Date: Mon, 19 May 2008 18:33:07 -0500
I appreciate the example. It's certainly reasonably elegant and to
the point, and it's more "real world" than some of the other ones
(bridging Cocoa to another language? yeah, right...a) it's not like
you can't interface between languages with other languages, and b)
this is not the kind of thing one is going to see in general
application code). But not the sort of compelling "we really need
the language to be this way otherwise it just doesn't work" example I
was hoping for
From what I gather, this feature of Obj-C provides two major things
you're missing:
1) It makes things more elegant and simpler. Yes, Java and C# can do a
lot of what Obj-C can do, but you said so yourself it would require
more code and be less elegant. Take any app of sophistication and this
translates to a lot of saved code and time since it adds up.
2) Many of the examples you're looking for are not so much in people's
apps, but in AppKit itself meaning that AppKit would have had to be
far more complex, big, and clunky if not for this feature.
So it may be a relatively minor thing in that other languages can do
what this does, but it makes a difference throughout Cocoa programming.
Alex Kac - President and Founder
Web Information Solutions, Inc. - Central Texas Microsoft Certified
Partner
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden