All OSes you mentioned support all of these ciphers either directly or via mcrypt.

This reduces the question to opinionizing: So here is my opinion - do NOT standardize (in the sense of hardcode) to any of those ciphers, but invest the on-time penalty to develop your apps and protocols in a way, that allows them to handshake the cipher used. This way you can trade speed for security now and are open for developments in cryptography (or cryptanalysis)

@SLaks - Yes, but only if the configuration of the server isn't updated to prevent this. When a cipher becomes dangerously weak, it can be disabled on the server side and a request for the client to upgrade their software can be shown.
–
PolynomialDec 21 '11 at 14:37

@SLaks Outright stupid implementations are not the idea's fault. As Polynomial already pointed out, it has to be the server who commands which ciphers are allowed. I also fail to see, how a hardcoded cipher would fare better, if the cipher were found to be insecure.
–
Eugen RieckMar 6 '12 at 20:18

@EugenRieck: That doesn't stop MITM; both sides must have a cipher blacklist.
–
SLaksMar 6 '12 at 20:20