> "you can define assets in pure python using any framework or engine you want."
sounds flexible but what does that actually mean in practice? are there guardrails to keep things interoperable
> "engine-agnostic execution"
how that holds up when switching between, say, pandas and spark. are dependencies and semantics actually preserved or is it up to us to manually patch the gaps every time the backend shifts?
sounds flexible but what does that actually mean in practice? are there guardrails to keep things interoperable
> "engine-agnostic execution"
how that holds up when switching between, say, pandas and spark. are dependencies and semantics actually preserved or is it up to us to manually patch the gaps every time the backend shifts?