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:
> The plugins are also very flashy with tons of animations, colors and emojis, which to me is just distracting
I also have seen that the very first time I tried neovim. Some people may like it but I consider a terminal to be as simple as possible. Furthermore, I use often the CLI on non-GUI terminals where such non-ASCII characters can have various side effects (e.g. unicode bars, braille like progress bar and so on, those destroy your serial terminal line).
I have tried several times and I always switched back to vanilla vim. Neovim has various nice features but it requires a lot of time to migrate correctly IMHO. 20 years of habits are hard to leave, I think.
Sure the configuration file is retro compatible, but some of the plugins are better suited for neovim and vice versa. I use a dozen of them and if I switch permanently to neovim I'd like to start fresh using more "modern" alternatives that make use of the newer features.
When I use a different editor, there will be lots of jjkk or ,w (I nmap ,w to :w). Habits die hard.
Now I switched to neovim due to the amount of good features I like with it. I use exclusively mini.nvim modules that are awesome.