Hi @Gareth Dwyer! The short and sweet is that while Airflow 2.0 did introduce some performance improvements and nice API enhancements (which may look surprisingly familiar to Prefect users haha), the thrust of the original âWhy Not Airflowâ post was about core architectural constraints, none of which were addressed or modified for 2.0. As such, we donât see any new use cases that Airflow 2.0 can handle that Airflow 1.0 couldnât, but Iâm sure the enhancements were nice for already existing Airflow users. (And to be honest, I get the sense that â2.0" was used more for marketing purposes than to signify features worthy of such a version bump).
Iâll DM you with my contact info if youâd like to dig deeper / go point-by-point or anything - Iâm definitely happy to help you in whatever way makes sense!