Affine transform multiplication is applied in the wrong order

[GuyPerfect]

Per this post, multiplying two affine transform objects appears to be done in the wrong order:
specifying a * b gives the result of b * a.

[dwineman (Dan Wineman)]

Not a bug. See here:

Transformation Order

This isn't a bug, but it's an area that's open to some degree of interpretation. When you compose two affine transforms A and B, you're asking for a new transform C that has the same effect as applying A and B in sequence. The API achieves this by multiplying their matrices together, which works because matrix multiplication is associative, and the order of this multiplication matters because matrix multiplication isn't commutative. But either order can be valid depending on how you apply the r…

[GuyPerfect]

Just this once I would like to appeal for reconsideration. My reply in the other thread outlines my concerns regarding existing game developers pivoting to Playdate.