Did you read the article?
The problem is that someone trying to bruteforce your MD5 hash won't add that sleep(500). Bcrypt is slow by design.
I thought the attack was against the application. The article talks about the security of the raw data in the database. I missed that on my first read. Sorry for that.
Is that it? bcrypt is good only because it is slow? In that case, why don't we use whatever we like (MD5, SHA1, SHA256, SHA512, SHA-3, etc) and add a sleep(500); just before the call? It is guaranteed to keep up with Moore's law as well!