blag commented on PR #23335: URL: https://github.com/apache/airflow/pull/23335#issuecomment-1112626838
Having a delay for a command - without asking the user anything - is okay IMO. Annoying the user into keeping up-to-date is verging into Dark Pattern territory but isn't there (and also, keeping up-to-date isn't a bad thing, and definitely helps the user avoid further issues). Good to hear that there are escape hatches for power users. :+1: If we're targeting non-power users, and if we're prompting users for input, then we should at least give the user time to read it before carrying on. Doing so will also hopefully get them to understand what the command is doing, which will aid in onboarding users. Bulldozing over their consent anyway just trains users to blindly run commands without understanding what the commands are doing. That's not helpful to anybody. So to sum up my point: if we're going to go through the trouble of asking the user for input _at all_, we should actually care about their informed consent/response. -- 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]
