Modifiers, Sockets, Images - Executed Bottom To Top

tldr: Modifier/Socket/Image on the top of the list to be executed last, not first.All calculations in Blender are made from top to bottom - that includes Modifiers, Textures and Nodes. This is logical - code is read from top to bottom, so the thing at the bottom will be fired last.But is it?It is when we think code-wise. When we think in terms of metaphors - not so much. A metaphor usually used for effects in interface design is that of <em>covering</em>. You have your base object, and then you <em>cover</em> it with effects (that would be Modifiers). You have your base image, and you <em>cover</em> it with layers (that would be Textures, Nodes dealing with images, and maybe someday true image layers).The bottom to top order is defined by logic and reality. In the physical world to overlap something, you place it on the top of the stack. In Blender to <strong>over</strong>lap, you place it <strong>under</strong>neath. It's contrary to the point the English words are backward.
The top-down system doesn't bring any advantages that I can see. On the contrary - it causes problems. When you connect an image node over another image in the Mix node, it goes <em>under</em> that image. So you have to connect it like this:
When you have a half-transparent decal texture, you have to put it <em>under</em> your main texture.
The texture that is on the <em>bottom </em>of the list in the Properties Editor is the one on <em>top:</em><em></em>This is another area where Blender is inconsistent with the rest of the artist’s toolset. For info on why this is bad, check here.It’s also another area when it’s inconsistent with itself - the VSE channels work from the bottom to the top.
Firing lists from bottom to top would solve these problems.