alt Hacker NewsThe part in this that I most question / deviate from is what I've quoted below about having distinctions (syntactically?) between objects and operations. Conceptually, it's a good distinction. But is it so clearly wise to bake in that distinction into the formal framework when doing calculations or proof?
> Most of the time we think of complex numbers as vectors in R2 or as rotation+scaling operators, but rarely do we actually we want them in both roles at the same time. So it is not very natural to equate the two objects, as opposed to finding a correspondence between them.
> So GA ends up being very stuck because it equates “vectorial objects” and “operators that act on vectorial objects”. It would be better to express all the geometric objects you care about in their most natural forms, and then find isomorphisms between them when it’s necessary to do so. Otherwise all the meanings get blurred together and it’s very confusing. So that’s another problem with geometric algebra: eliding the distinction between vectors and operators is undesirable, confusing, and disingenuous.
One finds in regular vector algebra that "position vectors" and "displacement vectors" are sort of two distinct types of objects, and that it is never physically valid to add two position vectors together unless you create an affine combination like (a+b)/2. A position vector 'a' is really 'O + a', so [(O+a) + (O + b)]/2 = O + (a+b)/2, another position... but a+b on its own would really be (O +a) + (O + b) = 2O + a + b, which is not geometrically meaningful. So positions and displacements might both be elements of R^2, mathematically speaking, but there is something physically different about them, which physical applications/geometry forces you to contend with. I think it is something like a historical accident that there's not a great notation for expressing this in normal mathematics (or at least, I'm not aware of one!).