> On Dec 12, 2017, at 2:40 PM, Jonathan Mitchell <li...@mugginsoft.com> wrote: > >> On 12 Dec 2017, at 19:56, Richard Charles <rcharles...@gmail.com> wrote: >> >> I always assumed the reason bindings never came over to iOS was they >> consumed too much cpu power and were too difficult to understand. It seems >> evident that 10 or 20 years from now Apple anticipates the bulk of it >> programmers coming out of school will use iPads with the new style >> documentation. Cocoa bindings do not fit very well into this picture. > I am not sure if stringent power concerns were the overriding factor for > excluding bindings from iOS. > Bindings are driven by observations, which do exist on iOS.
I stand somewhat corrected, I did not know KVO was available on iOS. > Bindings are actually a fairly essential technology for medium to large scale > data driven macOS applications. > Trying to manually glue hundreds of controls and data paths together quickly > becomes a major development obstacle. Amen to that! --Richard Charles _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
