If LinkedIn, the article's whipping boy for bad password storage, had somebody with the brains and capability to purchase and integrate this multi-machine password storage system, LinkedIn would have had somebody with the capability of implementing a secure password hashing system like pbkdf or bcrypt or scrypt and wouldn't need to buy a mega priced security solution from RSA.
LinkedIn is written almost entirely in Java, so Devise would not have worked out that well. Using something like jBCrypt would have been almost as easy, though -- if they'd thought of it from the beginning.
The failure here is just that whoever wrote the auth code didn't know that it was a problem, or thought (incorrectly) that using something like bcrypt would be significantly more effort.
