bolkedebruin commented on PR #26486: URL: https://github.com/apache/airflow/pull/26486#issuecomment-1306901163
So, it is too bad that we are now stuck with a confirmed bad situation because we seem not to be able to decide between option A and option B. I suggest accepting the change by @BasPH (it's an improvement) and if @potiuk wants to do a follow up that can be a subsequent PR (also an improvement). Let's get out of the bad situation first and let's not let get perfect get in the way of good. For the discussion: I think we should assume familiarity with Python for people coming to Airflow. Afterall, if you would like to use Airflow it requires python code to write a pipeline. As Python has a much larger ecosystem than Airflow and the "classic" style is basically a DSL on top of Python. That's an extra cognitive load as I basically need to learn another language. Therefore, I am in favour of exposing Taskflow as the default as it is more natural to Pythonistas. The classic approach is, as mentioned, a DSL and an opinionated way of doing certain things. This is great if you want a certain kind of standardization or want to limit what people can do (hey maybe we should even have a policy that only allows certain operators and disables taskflow for those use cases!). (And maybe this should be on the mailinglist :-P) @BasPH can you please rebase? -- 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]
