In 3D space, rotors are quaternions with different labels. If rotors are better, then the only conclusion we can draw is that people don’t like the name “quaternion”.
I mean if you're in highschool and poking under the hood of Roblox or whatever to write your first mod, rotor is a better name for the thing that manages rotations than quaternion.
I would go for something like “orientation”. Or “rotation”. Ordinary English words that represent what are, more or less, ordinary, familiar concepts.
The fact that it’s a “quaternion” or a “rotor” is kind of an implementation detail.
Of these four terms, Quaternion is the most precisely correct. The reason is that rotors are, by definition, constrained. Quaternions can take any value. Due to floating-point precision problems, your rotor will not always be exactly a rotor, but may some multivector which is not a rotor.
This is kind of like representing a point on a sphere using (x,y,z) coordinates. You can call it PointOnSphere or Vector. I would rather call it Vector, because PointOnSphere implies a constraint which won’t be exactly satisfied, and I want to be reminded of that fact. The type name (Vector here, and Quaternion above) represents the object’s structure and the constraints which are actually enforced by the underlying representation.
