Author here.
Same same but different.
K3d is focused around simplicity and recourse saving mostly due to it using k3s instead of pure upstream Kubernetes (like kind).
Meant for local development with Kubernetes from the beginning, when kind was mostly focused on E2E for Kubernetes itself.
There's more to it, especially in the way both work and what they support.
Maybe I can do another post on that soon.
