Behaviors vs Scripting

#1 Right now?

Neither... For the iPhone you need to make your game directly out of coding (they are trying to fix the fps issue).

But here is the good side and down side on behaviours vs scripting:

Behaviors:

Easier to apply
Takes less HD space
Needs more processor energy.


Scripting:

Harder to apply
Takes more HD space
Uses less processor energy.

Anyway, processor power is not a big issue, so HD space could be just another bonus (but 1 or 2 MB isn't a big deal).

I suggest using behaviors, I never learned how to make behaviors, but I bet it is much easier.

#2 @Tyler
For HD space, vanilla script take less than behaviors. But we're talking about amounts under 1MB. It doesn't matter either way.
Also, I don't think behavior is easier to apply at all, as soon as you try to make your own (meaning: right away, because you can't realistically make any game without making your own scripts).

Scripting is not harder than behavior, it only depends if you want class based scripts or something class independent like behavior (but without the advantage of inheritance). But the difference between the two is not big.

I prefer vanilla scripts, because it is how torqueScript was designed to be used from the beginning, but it is mostly a matter of personal preference.