News for hackers. Stuff that matters.
Re:Show HN: A simple, fast and user-friendly alternative to ... by bm1362 on Sunday October 08, 2017 @06:01PM (#15430234)
That was just a hyperbolic example, but I can think of a few superficial reasons:

1. Because you end up with a more complex Dockerfile. I've seen curls, clones etc during build - having a remote call for random tools in our build _feels_ like a bad practice.

2. There is also the issue that a fleet of application servers will have different tooling available, which can be frustrating in a pinch. I've done some gnarly things across many hosts, expecting a common set of tools. At AWS, we were responsible for non-nuclear team's services during oncall and would ssh to their boxes. Logging into a box with a different shell would be annoying.

[2] > for i in `cat hosts.txt`; do ssh $i '...'; done

Re:Show HN: A simple, fast and user-friendly alternative to ... by Tyr42 on Monday October 09, 2017 @09:33AM (#15433617)
I mean you wouldn't need to set fish as the default shell. But even if it was, you could `do ssh $i "bash -c '...'";`