Cowsay should not be enabled by default (2015) (opens in new tab)

(github.com)

11 pointsmuscaw3y ago7 comments

7 comments

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.

barnabee3y ago

Totally agree

It’s sad that so many people would rather avoid any form of individuality or fun than risk having to tolerate someone else’s idea of fun that they don’t like.

4gotunameagain3y ago

Sometimes it has to do with people not having much more to offer other than a professional appearance :)

This is not always the case of course

bravetraveler3y ago

I don't think the Git issue framed it well. Pinning this on a single meeting or interaction makes it easy to trivialize

As someone who uses Ansible a lot, I giggled. Once.

Afterwards I figured out how to disable it because the novelty was gone. The output this creates is a slog.

Now I 'have' to remember to create Ansible.cfg files across countless projects because someone thinks this is that funny.

That's the most portable approach; it's the best way for contributors. Otherwise I'd set the environment variable on all of my shells and call it done.

I forget so often that I've been trained to cancel a playbook as soon as I see a cow from fact gathering.

It's more of an annoyance than a real problem.

Anyone with cowsay installed on their controller (this isn't always a workstation or human) is initiated in the 'know how to disable this' crew, and gets to regularly attend meetings

I feel the feature would work better randomly appearing. Maybe make it visually useful, automatic on the slowest-known run.

It retains the novelty because it isn't a constant.

karmakaze3y ago

I like levity. I value my vertical text space even more.

bravetraveler3y ago

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

aasasd3y ago

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.

j / k navigate · click thread line to collapse

7 comments

johnklos3y ago

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?

barnabee3y ago

Totally agree

It’s sad that so many people would rather avoid any form of individuality or fun than risk having to tolerate someone else’s idea of fun that they don’t like.

4gotunameagain3y ago

Sometimes it has to do with people not having much more to offer other than a professional appearance :)

This is not always the case of course

bravetraveler3y ago

I don't think the Git issue framed it well. Pinning this on a single meeting or interaction makes it easy to trivialize

As someone who uses Ansible a lot, I giggled. Once.

Afterwards I figured out how to disable it because the novelty was gone. The output this creates is a slog.

Now I 'have' to remember to create Ansible.cfg files across countless projects because someone thinks this is that funny.

That's the most portable approach; it's the best way for contributors. Otherwise I'd set the environment variable on all of my shells and call it done.

I forget so often that I've been trained to cancel a playbook as soon as I see a cow from fact gathering.

It's more of an annoyance than a real problem.

Anyone with cowsay installed on their controller (this isn't always a workstation or human) is initiated in the 'know how to disable this' crew, and gets to regularly attend meetings

I feel the feature would work better randomly appearing. Maybe make it visually useful, automatic on the slowest-known run.

It retains the novelty because it isn't a constant.

karmakaze3y ago

I like levity. I value my vertical text space even more.

bravetraveler3y ago

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

aasasd3y ago

j / k navigate · click thread line to collapse