understanding why podman-compose does things differently than podman itself

This is not a bug report but an attempt to understand podman-compose better.

From some experiments I understand that podman itself
- supports pods with own namespaces, i. e. containers inside one pod can talk via the loopback interface
- creates an infra container inside a pod to keep the pod and its resources up and running

From what I see, podman-compose does that differently:
- pods don't contain an infra container
- pods get their own network assigned and every container gets an own IP address

I can get podman-compse to create an infra container as well by setting `--pod-args='--infra=true --share=""'` (can I set this in the compose.yml as well? Otherwise I need to change the systemd unit file as well). I can bind different container (services) to the same IP address by setting `network_mode: "service:"` in the compose.yml file. I understand that in case I need to bind different services to the same port numbers I need different IP addresses and can't work with just one loopback address (but I still could use different loopback addresses in that case).

I'd like to understand what podman-compose all does differently than podman and why it does so - what are the benefits and maybe issues?