yeah, it’s not a typo in the title, but it’s almost true!
Flash’s own functions and/or method are slow as I can say. I first noticed this while having a look at TweenLite’s easings.
Math.pow is slow. It’s faster doing x * x * x and so on – yeah really! Don’t believe me? Give it a try!
I assume this behaviour not only to sin, cos and other trigonometric functions (as already found out to be right by polygonal labs), but also to Flash’s own graphics-library.
So I’m on trip atm where I’ll do EVERYTHING myself. I’ve already done a small Bitmap-based Font-Engine, Textfields, unbelievable fast OBJ-Parser and a lot of more stuff… just wanted to let you know this :D (if anyone reads this at all – I dunno)
I also think about y everyone doing flash 3d on this planet, uses sin/cos and so on with radians, instead of creating a lookup-table “once”. horrific – it’s just that what’s done in code these days… ugly code! ever had a look at papervision, away3d, and some more google code project? blehyawk.
enough for know – have a nice day :)
22:21, 6. May 2010Felix /
Hell yeah – sometimes I read this. I know that as sometimes give their developers a hard time on trying to get rid of the lack of speed.
But, as I can say, just think of this as a kind of a personal challange to kick her in her cute ass.
Man,
rock on.
13:19, 27. October 2010wonderwhy-er /
I often try to stay away from using core methods and classes where performance is of issue. Like say x|y properties on DisplayObjects are actually getsetters that modify transform matrix. It’s worse case scenario but anyways in performance critical cases I try to test such stuff that usually brings me to not using core classes.