webtiming / timingobject

Defines the HTML5 Timing object at the basis of multi-device synchronization matters
25 stars 4 forks source link

State Vector Attributes #6

Closed ingararntzen closed 9 years ago

ingararntzen commented 9 years ago

The state vector attributes are full names vector.position vector.velocity, vector.acceleration, vector.timestamp

These long names are very unpractical as these properties are used frequently. I would like to see them shortened vector.pos, vector.vel, vector.acc, vector.ts or vector.p, vector.v or vector.a, vector.t

I've used array indices before (vector[0], vector[1], vector[2], vector[3] ), but I suppose letters are far more readable

Snarkdoof commented 9 years ago

I support shorter names, pos, vel, acc and ts is more to my liking due to a nice tradeoff between compact and readability. On 16 Jun 2015 13:49, "ingararntzen" notifications@github.com wrote:

The state vector attributes are full names vector.position vector.velocity, vector.acceleration, vector.timestamp

These long names are very unpractical as these properties are used frequently. I would like to see them shortened vector.pos, vector.vel, vector.acc, vector.ts or vector.p, vector.v or vector.a, vector.t

I've used array indices before (vector[0], vector[1], vector[2], vector[3] ), but I suppose letters are far more readable

— Reply to this email directly or view it on GitHub https://github.com/webtiming/timingobject/issues/6.

dontcallmedom commented 9 years ago

in general, short names are left as an exercise to the IDEs or to libraries; they otherwise hinder readability and discoverability.

Another way to look at it is that there a lot more people that will need to read a given piece of code than there are people that will need to write it :)