|
|
|
|
|
|
by jacobolus
3606 days ago
|
|
|
Gradians are absolutely terrible. For everyday use, radians are also pretty impractical. I personally like just writing fractions of a full turn, but degrees/minutes/seconds aren’t too bad. There are two cases where linear divisions of arclength-measured angles make sense: (1) the angles to make regular polygons of low numbers of sides, (2) repeated binary divisions, whose cartesian coordinates can be computed easily because we can just add two vectors and renormalize using an inverse square root which we know how to efficiently compute, and which are then nice for fixed point representations using binary integers in computers. For the first case, I think rational fractions of a turn work best; for the second case, I like binary angles (“brads”) https://en.wikipedia.org/wiki/Binary_scaling#Binary_angles ; losing the ability to precisely represent a thirds of a full turn is just one of those trade offs you sometimes need to make. Otherwise, treating angle as a linear quantity with precise measurements (instead of some kind of approximations) is for most problems less useful than just using a cartesian coordinate representation for an angle (possibly keeping track of the coordinates squared if we want to stick to rational arithmetic.) Radians are only really useful for solving calculus problems by hand, or writing academic math/science papers where it’s important to stick to established conventions. For practical computation radians are almost always an inferior choice, more computationally expensive and less precise (they’re built into lots of existing libraries, so can often be convenient despite the inefficiency). |
|
|