What I don’t like about Intel’s syntax is that the normal phrase is ‘move A to B’, but ‘mov A, B’ moves what’s in B to A.
(The reason I don’t like it may be because the first CPU I programmed was a 6502, which had separate load and store instructions. Unfortunately, that doesn’t work well with memory-to-memory (which the 6502 doesn’t have) or register to-register (for which the 6502 used a T for ‘transfer’, as in TXA for ‘copy X register into Accumulator) instructions)
So that tradition might have been where most programming languages picked the convention up from?
Ie so that it becomes T := N / (p * V) where N is measured in number of molecules, not in number of moles.
So we'd measure temperature in Joule (or electron-volt) per degree of freedom.
Also, GNU as assembler has switches to allow Intel syntax if that's what is desired.
So MOV is literally "move into this register I can access, this value that I can't access until it in a register."
For example, a wordy version of how I think through MOV AX,5 could be: "move into AX, the value 5" where AX is an accessible container for the value 5.
I did assembler coding for more than a decade, so I'm pretty nostalgic about it. Nothing I do really calls for it anymore these days.
I've always thought AT&T syntax is made for machines & debugging compiler output while Intel syntax is made for people and large scale coding...
Tangential but I like to see this as sort of two ways of thinking where the operands are in both cases ordered so that what you “have” is closer to “you”.
So in Intel syntax it’s like you are thinking from the CPU perspective and what you “have” are places that you want to put data into. So dst, src.
In AT&T syntax it’s like you are thinking from the perspective of a program, and what you “have” is data that you want to put into places. So src, dst.
I’m not suggesting that this is the reason mind you. Just saying how I like to think about it.