Which exhibits exactly the failure scenario outlined in the article; partway through the script RVM cleans up after itself by running "rm -rf ${rvm_src_path}"
You're right, I'm completely wrong - the worst thing that can happen here is that the whole RVM directory is removed. Hardly catastrophic, and definitely not the extreme failure case the article is talking about.
http://rvm.io suggests you run the command:
\curl -L https://get.rvm.io | bash -s stable
Which exhibits exactly the failure scenario outlined in the article; partway through the script RVM cleans up after itself by running "rm -rf ${rvm_src_path}"
Simple changing this to
"\curl -L https://get.rvm.io > /tmp/rvm.sh && bash /tmp/rvm.sh stable"
Would eliminate the potential for nasty failures, with a minimum of fuss.