A better answer to the problem is to not have password requirements because it's the user's responsibility to choose a secure password. If their password is compromised because it was their dog's name or "password1234" then it's their fault.
A way to engineer against brute-force hacking is to limit the number of attempted logins per username and IP. If they hit the limit then their account should be locked or their password should be automatically be reset with an email.
While I agree with you on some level, this is quite contrary to the spirit of our times. Plenty of otherwise smart people have pretty dumb passwords. I'm similarly ignorant of enough things that I don't judge them as simply deserving what they get.
It's hard to answer a question phrased this way because there can be any number of reasons why a useful feature is not implemented. Time constraints, budget constraints, process constraints, organizational constraints ... and then somewhere in this long list is, "Gee, we just never thought about it."
Perhaps a more interesting question is:
Among those of you who believe that providing password requirements up-front is a useful feature, did you implement that feature in past projects? If not, what prevented you from doing so?
1: if your site is uncluttered -- that is, it hides non-essential information -- it will be more appealing to the user;
2: if your site is following practices common to other sites, the average user will have already learned those practices before coming to your site;
3: if a specific user demonstrates a need for guidance/non-essential information, that information should be made explicitly available.
Applied to password requirements:
- Show the password field without requirements (uncluttered initial state)
- If they enter a valid password, all is well (happy path)
- If they enter an invalid password, surface the requirements (explicit guidance)