potiuk commented on PR #37609: URL: https://github.com/apache/airflow/pull/37609#issuecomment-1966554895
Looks like Chat-GPT generated response. No time to read it, so I shortened it with Chat GPT: ``` Initially skeptical of Airflow, I found it cumbersome and lacking conceptual integrity, akin to scattered building blocks without a coherent design. However, a revelation came when I unearthed a pure Python solution buried deep within Airflow's documentation, utilizing only the @dag and @task decorators. This discovery transformed my perception, turning Airflow from an annoyance to an indispensable tool. Motivated by this experience, I crafted a new introductory approach, emphasizing the simplicity and power of the decorators. Despite suggestions to include the >> operator, I found it confounding and incongruent with typical programming flow. Presenting both approaches risks confusing new users with unnecessary choices, particularly through a GUI interface. Therefore, I advocate for a streamlined introduction focused solely on the decorators, aligning with Airflow's architectural elegance and ensuring a smoother entry for newcomers without unnecessary complexity. ``` This has been discussed multiple times and your point of view is only of yours. Airflow has multiple different kind of users - both experienced Pythonistas and people who are just data scientists and don't care too much about python - they want to put their DAGs from existing building blocks (i.e. operators) That's why - what we are asking you to make the first page in the way that appeal to both kind of users - and the tab switching of different ways of programming with Airflow is a good idea. You have to accept the fact of life that other people have different experiences and think differently - and Airflow does not have to respond to your mindset only, but also to other mindsets and our direction guiding you there make it so. Even if not perfectly fitting either, making it appealing to both is our goal. Kind request to adjust to those expectations. -- 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]
