I had to force myself not to.

If this is done using SIMD instructions then there isn’t an extra cost for the fourth component divided by 2 (if that’s what you were referring to by optimizing out).

And IMO angles in degrees and radians should technically be stored in different types because they are different units. But we didn't start out with such rigorous type structures so now we are left with people accidentally mixing degrees with radians.

You mean packing Euler angles in Vector3? IMO people are only doing it because Vector3 happens to hold 3 floats, the same way people use Vector3 to represent 3D points. They are a parameterization of orientation and technically should be a different type.

Right. This is indeed an annoyance. For my use cases at least (mid point, weighted average, lerp, etc.), I created helper functions that bypass usage of origin.

BTW this video was what prompted this search.
www.reddit.com/r/NatureIsFu...

Just a few sphere brushes oscillating in sine waves.

TIL the acronym FUI. Thanks and this is beautiful.

I mean if you squint you can kind of see the axes pointing away from you…making this right-handed.