What is the logic behind having the MAC address come first when decapsulating?

Question

Computer networks

Guys, something blunt wild. When encapsulated on the last wire by Ethernet, the poppy address of the recipient is put in the header. Accordingly, during decapsulation, the first thing that is read at all is the poppy address.
What is the point when a frame travels from one node to another (they are not on the same network) to specify the poppy address first, if it would be more logical to specify the IP so that the frame finds the desired network, and then finds the desired node in this network by poppy address.

Answer 1

What is the point when a frame travels from one node to another (they are not on the same network) to specify the poppy address first, if it would be more logical to specify the IP so that the frame finds the desired network, and then finds the desired node in this network by poppy address.

If the recipient is not in our network, then in the L2 header, the recipient will be the router, not the final recipient.

Answer 2

at the level of abstraction of the network stack where the decision is made to route the IP packet to the desired network (L3), the packet is already rid of MAC addresses. and in order for a packet to reach this abstraction level, the packet must first be correctly processed at the previous abstraction level (L2), which is where MAC addresses are required.
the decision on which computer the network will send the packet to (its own or transit), ultimately always relies on the destination MAC address (the MAC address of the final recipient or the MAC address of the router), this is the last thing that becomes known before sending the packet, and the first thing that is requested from the incoming packet, so the destination and source MAC addresses come first and not anywhere else.