You might have been joking, or you might have been serious. If you were joking, my reply is for the benefit of readers other than yourself.
Aside from the obvious risks of downloading and immediately executing internet code, which are indeed risks but of course we all accept them on a regular basis...
... and aside from the mildly more subtle risks that the HTTP server is doing something sinister, e.g. with browser-agent, and so you're not getting the code you think you're getting...
... even aside from these issues, curl-and-pipe-to-sh is dangerous because of its failure modes.