The day I'll have to use an AI will be the day I either resign to be developer or quit my job. My company first disallowed AI and now they say "if you don't keep up we will pay that off someday" and I disagree and stand by that I'll never touch any AI stuff.
My knowledge, my experience and my passion to development is made from tinkering, failing, retrying and challenging. When a friend or colleague ask me a question there is a high percentage I can already fix the issue just by the experience I've accumulated (obviously, if the question is in an area I already explored, I'm not a book).
Thus, I don't want to be integrated in this new AI world and I feel like someday I'll have to do something else as even companies will tell people to use AI by the fact "you should be more productive and cost less". No, AI is a mental disorder.
Though most of the software do the right thing by checking if the standard output is an actual tty (isatty) to avoid colors when redirecting to something else (e.g. socket, fifo, etc).
The name NO_COLOR suggests a really binary choice which may be okay. Though GNU coreutils usually have a more selective option like --color=always|auto|never.
I'd prefer supporting a more general COLORS=on|off|compatible|...
Meaning:
- on: always on even when redirecting
- off: fully off
- compatible: maybe something like on by default and off if redirecting to a non-tty
> Prompt for user input. If a user doesn’t pass an argument or flag, prompt for it. (See also: Interactivity)
prompting is usually the worse choice in a command line utility. on error you lost what you've type and have to copy back and forth unless the terminal disappeared.
> Prefer flags to args
Options are designed to be... wait for it... optional. as the name suggests. If you actually require to pass at least one option to a command to get it working then it's bad designed. An option is there to change what a default is not suitable for you.
For example, tar uses -x, -c to determine what to do. We're all used to it now but that is not the way we should design a command. A correct way is more like tar/untar similarly to zip/unzip. That would make more sense.
To me, rpm is definitely the worse in terms of use of options. If I'd redesign it I'd imagine something like:
I think removing a joke to be considered as corporate is a bit exaggerated.
It's okay to have "fun". I consider a software more corporate when it has a large website with dozen of MB of Javascript, analytics, XML documentation, ten automatic bots with CI checking every part of a merge request and a contributing guide larger than the whole got documentation to be more corporate than a clean and simple UX without jokes.
Remember: a clean UX should present output only when necessary. This is exactly where I prefer a lot hg status than git status for example.
Do I miss something? I've been following the project since the beginning and just checked the wiki, the website and all over the documentation and haven't found something relevant to anime.
I'm more of a mercurial guy (since 2009) and I honestly never understood the success of git with its total nonsense of options, UX and documentation. Each command does too much thing and has different behavior. Type git diff -x and git switch -x in a non-git repository and check the output...
I use IRC every day, in fact it's the best way to communicate for techies IMHO, focus on the content and no gif, emoji, images and all other nuisances that you'd get on any other platforms. I've written my https://projects.malikania.fr/irccd/ bot for various tasks. Long live IRC.
