Cowsay should not be enabled by default (2015)

by muscawon 5/7/2022, 9:21 AMwith 7 comments

by johnkloson 5/7/2022, 10:20 AM

Seriously, people need to chill the duck out. If a presentation needs to be so incredibly serious, then why blame others when you should've run through it at least once yourself?

Why do people think that "serious" and seemingly "professional" should outweigh levity in life? It's not too different than worrying about dress code: it's anal to an extreme that doesn't help anyone.

by bravetraveleron 5/7/2022, 12:58 PM

I would've supported this

I have cowsay installed on random systems for the occasional novelty. There's no case where I want it consistently

It makes the output a slog except for the shortest and simplest of plays... and is surely confusing for new users.

The default to use it means I have an unknowable number of `ansible.cfg` files spread across projects with exactly two lines:

   [defaults]
   nocows=True
Routinely making more when I'm inevitably reminded of the parameter... because I'm using a new project on a controller that happens to have cowsay installed

I could set the environment variable for my shell... but it's not as portable (eg: contributors would have to do the same)

I'd find more joy from this if it was random, say 1/10 runs

Most people know about this parameter against their will. This fun is more burden than fun.

It comes off more like a forced joke that everyone needs explained

by aasasdon 5/7/2022, 1:08 PM

The proper reaction to Ansible's use of `cowsay` is to have it enabled when copying output to file an issue or a comment on Ansible's tracker. Even better would be to use an animated ‘terminal’ gif with special effects, since the authors like fun so much.