[This is simply for documenting how good the future improvements of LC 7.0 are ...]
LC 6.7.1 = 125 milliseconds, LC 7.0.1 = 1888 milliseconds, a factor of round 14.
The factor with the 6.7.1 script (using bytes or numToByte/byteToNum, no char-syntax) was close to 25 when using 7.0.1. Only by switching to new features of LC 7 (for example combining an array by a multichar string) I could bring the factor down to 14.
No further comment.
Upper part is a usual field, lower part is a polygon graphic, derived from the field by "tracing" maskdata from a snapshot and then transforming the polygon. Pretty fast with LC 6.7.1, fast enough to be done "live" with every keydown (typing). With LC 7.0.1 it's for rather "static" use only.
Factor 14
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: Factor 14
When speaking about speed losses or speed improvements one could use such an example for discussing the "scale" for comparisons. What is more appropriate, a "linear" scale (differences) or a "proportional" scale (factors)?
Here, fore example, 125 ms against 1888 ms for a special task.
Some of you may say: Two seconds for such a task is fast enough, I use this never or seldom, I don't mind.
Others may say: This is inacceptable, a factor of 14 is an increase of 1400%. I need such tasks or similar ones often, my time budget isn't wide enough to cover this.
For me both arguments are good, depends on the personal situation. Perhaps we should use both, in parallel, display/denote absolute values (differences) and proportional values (factors).
Say the increase of time needed for a special/typical task is from 1 second (6.7) to 14 seconds (7.0). Then everybody can judge whether he's willing to pay this prize for using LC 7:
I already contributed. Makes me feel somehow more "enabled" to criticise -- or praise, if applicable.
Here, fore example, 125 ms against 1888 ms for a special task.
Some of you may say: Two seconds for such a task is fast enough, I use this never or seldom, I don't mind.
Others may say: This is inacceptable, a factor of 14 is an increase of 1400%. I need such tasks or similar ones often, my time budget isn't wide enough to cover this.
For me both arguments are good, depends on the personal situation. Perhaps we should use both, in parallel, display/denote absolute values (differences) and proportional values (factors).
Say the increase of time needed for a special/typical task is from 1 second (6.7) to 14 seconds (7.0). Then everybody can judge whether he's willing to pay this prize for using LC 7:
- (Uses difference). The 13 seconds for some user A once a week or month may not matter.
- (Uses factor). The time increase for another user B for such tasks, from half a working day per year to 7 working days per year will certainly matter.
I already contributed. Makes me feel somehow more "enabled" to criticise -- or praise, if applicable.
shiftLock happens