Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

BadWolf13

macrumors 6502
Original poster
Dec 17, 2009
271
0
I just recently learned about bindings, and the main advantage so far is less "glue code." Now what I'm wondering at this point, does this lack of glue code make the program run faster, or does it just make the programmer's life easier?

Keep in mind that while I'm writing small programs now, there is the possibility that I may write rather large programs in the future, and so this is knowledge I'd like to have beforehand.
 
I just recently learned about bindings, and the main advantage so far is less "glue code." Now what I'm wondering at this point, does this lack of glue code make the program run faster, or does it just make the programmer's life easier?

Primarily the latter.

It's possible that the use of bindings provides some efficiencies in some situations, but as an overall strategy for making a program run faster, I think it's mostly orthogonal. No one says, "Hmm, I have a speed problem. I know, I'll use bindings to fix it!".
 
In all likelihood code using bindings will probably be slower, not faster. But if you can measure the difference in your UI code then you are probably doing something wrong (or have a very, very complicated UI).

The way bindings speeds things up is that it is quicker to program in the first place (once you get used to them), and there is less code to troubleshoot and debug. So you can then spend more of your programming time concentrating on the parts of your program that actually could benefit from some optimization.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.