potiuk commented on PR #26486: URL: https://github.com/apache/airflow/pull/26486#issuecomment-1250960617
> This PR reverts a change made in #25657 to the Airflow docs home page. I understand the desire to push TaskFlow usage but don't think this is the right place. This is the very first piece of Airflow code a reader will see, and mixing multiple concepts adds unnecessary complexity. This example should be as simple as possible. How about in all the prominent "first time" places we promote both versions and clearly distinguish them and even explain who is the target for both ? I personally think writing taskflow api is easier/better for some groups of users and writing "classic" operators is easier/better for some other groups. And we do not know who reads this when they first see Airflow. So rather than choosing one or the other, maybe we should simply say: *`If you would like to compose your DAGs from "black-box` type of "components" - use **classic operator** approach:` Example here. * `If you prefer to write snippets of Python code in more functional way - use **taskflow** operator approach: Example here I think this would be much better and paint better picture of Airlfow in the mind of both groups of users and make Airflow feel much more modern (I have a feeling that promoting classic operators in the first page makes it more "old-school" and when we deliberately explain that both ways are equivalent and target to different kinds of users, it's not only showing teh 'modern" face but also showing that we delibereately gave our users the choice and even helped them to make the choice. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
