|
|
|
|
|
by a1369209993
2112 days ago
|
|
> If you take the geometric product of a force vector and a displacement vector, the result is the sum of a scalar and a bivector, both with the same units of [force]·[distance]. This part is where I have problem with GA: what the hell is the physical[0] interpretation of such a sum? For example, a four-vector <p_x,p_y,p_z,c·E_k> (momentum and kinetic energy) can be thought of as kinetic energy being the temporal component of (4-)momentum, but no similar interpretation seems viable to combine work and torque into a logically unified quantity. 0: I'm not sure if this is the right word - the interpretation as single unified value with no special-case treatment of its components might be another, equally not-quite-right way of putting it. |
|
Like with any expressive language (e.g. English, C++, or matrix algebra), GA makes it possible to state a wide variety of nonsensical things. But that’s not the fault of the language.
Where GA really shines IMO is in the ability to divide by vectors, something that is extremely useful but gets super cumbersome using other mathematical languages.
The biggest “problem” I have with GA is that it takes a lot of practice to get familiarity with all of the powerful stuff it can do. There are pages and pages of (extremely powerful and useful) short identities which are impossible to memorize by just looking at them, and can only be learned as far as I can tell through years of hard-won experience. I feel like I still only really have a handle on the most basic stuff.
I find regularly myself working on some complicated coordinate-based calculation for 3 pages of scratch paper full of mistakes and wrong turns, only to experience déjà vu, re-express the original thing in GA language, and end up with a clear and geometrically interpretable 4 lines of simple algebraic identities which solve the problem. But I’m not always sure if I’d be able to figure out which 4 lines to use right off the bat, without first going through the coordinate slog.