Saw this question yesterday on reddit (https://www.reddit.com/r/dataengineering/comments/r9cy2k/dagster_in_place_of_airflow/), thought it would be interesting if someone from the community could also give some comments there.

From my team's bakeoff about a year ago: Airflow is the OG in the space, it's well supported and has integrations with everything, but it's also just kind of a pain to work with.

I’d also be interested to see other people’s experiences/comparisons between Dagster and Prefect

This is a great idea. We’d love to have a few answers and then we could use this as a reference post for user-generated answers to this (as opposed from coming from Elementl.) @ramshackle-jamathon is going to submit a response.

Prefect only supported Dask for remote computation and IMO Dask should literally never ever ever be used. It's an entirely broken model of remote execution based on serializing code objects and sending them over the network. If you make heavy use of complicated C-backed modules in your Python code, expect Dask to explode when you try to version things.

I dropped a comment on that post that was mainly from the perspective of a data engineer writing a job, there's a whole other angle from the perspective of the infra/ops person managing the platform.