I see no real point in changing `transform.rot` into a Quat. As Ali said everything is already done with quats under the hood and the euler stuff is nice for the user. If the attribute type (or a subcomponen of it) would be Quat but we need to show eulers in the UI, we would need to hack lots of places.

Additionally all scripts tha use/set `transform.rot` would immediately break, no matter if the protocol change could be detected. I don't see any clean way around this?

Anyway, we should stick with this stuff :) Not sure if the ZYX order could be easily changed to XYZ as this is nowhere near "user space" code and would happen internally in placeable from `transform.rot`. But if there is no practical need to it, I would leave it.