dwreeves commented on issue #67515: URL: https://github.com/apache/airflow/issues/67515#issuecomment-4554902672
I vaguely remember finding a discussion some Airflow maintainers had on rich-click (a library which I co-maintain, hence why I was namesearching it) and they concluded they didn't want to add more things into the import path if they didn't need to, in fact that was the reason they were using _click_ not argparse, never mind rich-click. Since Click is so much better DX for incredibly minuscule overhead vs argparse, I assumed from this that Airflow was ok making some minor DX trade-offs in exchange for minor performance wins. You disagree with this, which is 100% valid, but this is something that formed my impression on the Airflow project's priorities. > If you feel so, I think you should read the comments again! My note of not contradicting was in reference to task execution related stuff. Yes I got dag processing wrong. Thank you for the lesson on how dag processing works! The task execution stuff was the main reason for any of this. The linked blog post from Armin is about people using AI to generate issues. My entire issue is human, I assure you. The only thing which involved AI is 100% disclosed, the optimization script. My issue certainly isn't "95% clanker-generated and largely inaccurate." You just think moving some imports to be lazy makes things harder to maintain and spaghetti. Which is fine. That doesn't make my issue nonsense. Surely you can see some difference between me and someone who is writing an issue after having learned about Airflow 3 hours ago. 😂 I am sorry I lobbed accusations that I was speaking to AI and not you. But it was just obviously AI-generated in some way, Pangram agrees (Pangram has a low FPR), and it was undisclosed. And ultimately, if I feel like I'm talking to AI, it feels like there is an asymmetry going on in what is being brought to the conversation. I do see that your most recent comment does not read as AI generated nor does Pangram accuse it of being AI. Thank you for that! 🙂 -- 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]
