Use shared keys like you would salt, sparingly and with lots of care and knowledge of how to use it.
As I wrote in my initial comment: It's not about targeted attacks, it's about evading netblock scans.
Use shared keys like you would salt, sparingly and with lots of care and knowledge of how to use it.
Bullshit. Use one password-protected keypair for each critical zone (work, personal, etc.). Keep it on your main machine and do not copy it to "places". Also don't spread FUD on public forums about the most secure ssh auth-option (short of multi-factor).
This is not a drawback of key-based authentication versus passwords because you have the exact same problem with passwords. If you want to explain proper key-management then explain it. But don't make it sound as if key-auth was some esoteric option that should be carefully considered versus password auth. Key auth should always be the default and password auth should always be disabled, exceptions to this rule are very rare.
No, there never was a debate. The two changes address different concerns and you should always do both.
You turn off password authentication to prevent targeted brute force attacks, keyloggers and (more common) accidents such as typing your password into the shell.
You change the SSH-port to improve your odds in case of a vulnerability in the SSH-daemon itself (sweep-scans tend to probe only the default port).