I can agree, but the terminal emulator is something I very rarely launch from the command line. I run it from a menu, or an icon. Maybe with keyboard but then its meta+T
The origin of the name are clear, but the name itself should describe what is it because these name can be find out of context.
These names can't be easily understandood without context. And these name will be found without context:
For exemple, you may meet this name in a process list. In this case you don't understand why the process "dwm" is eating a lot of gpu power.
A variable name can be short, because it's name will be found in it's context.
Suckless tools are meant for hardcore *nix hackers who already know how to look up this information, so no, the naming doesn't really matter. Anyone who knows how to use the ps command will also know the man command, so if someone wants to know what that dwm process is, they can just do "man dwm".
Is that a convention, or just what they stand for? (Do the window manager and the menu suck, because they don't have the "s" prefix? Is st static because it doesn't have the "d" prefix? Why do we abbreviate "terminal" but not "menu" / why not follow the established abbreviation of "term" as in xterm, dtterm, eterm, etc.? How come the "s" prefix in sprop and sselp stands for "simple" instead of "suckless"?)
dynamic window manager, dynamic menu, suckless terminal
The names are all very clear once you know the naming convention.