On the curl | sh pattern

This article completely neglects to mention the other dangers of this pattern, namely what happens when the connection drops mid download[1] or the server responds differently based on user-agent or IP[2].<p>[1] <a href="http://www.seancassidy.me/dont-pipe-to-your-shell.html" rel="nofollow">http:&#x2F;&#x2F;www.seancassidy.me&#x2F;dont-pipe-to-your-shell.html</a><p>[2] <a href="http://www.djm.org.uk/protect-yourself-from-non-obvious-dangers-curl-url-pipe-sh/" rel="nofollow">http:&#x2F;&#x2F;www.djm.org.uk&#x2F;protect-yourself-from-non-obvious-dang...</a>

RVM, pow, heroku, homebrew... all things I had to deal with as a Ruby developer. I was shocked at how often it is recommended when I had to set up a new Ruby dev environment on OSX.<p>Too bad seeing Rust following that trend as well. I was hoping new platforms would evolve past that

<a href="https://get.docker.com/" rel="nofollow">https:&#x2F;&#x2F;get.docker.com&#x2F;</a> does this too. Though I feel like they do a much better job than Adobe, when I download Flash from http and don&#x27;t know what the installer does.