When JSLint hurts your feelings, hug it out with Doug.

0. There are some situations that are difficult to distinguish mechanically, so I now consider all of those cases problematic, even when they are not obviously wrong.
1. You should be coding for readability and error resistance.
2. The place to express yourself in programming is in the quality of your ideas, and the efficiency of execution. The role of style is the same as in literature. A great writer doesn't express himself by putting the spaces before his commas instead of after, or by putting extra spaces inside his parentheses.
3. Many people think they have good reasons for doing things badly.
4. The purpose of JSLint is not to make you feel good about inadequate coding standards.
5. You are presuming the whitespace at the end of a line is either trivial or harmless. ~Austin Cheney
6. JSLint is not able to determine which cases are troublesome and which are useful, so it warns on all cases.
7. It is easy.
8. It seems like good advice.
9. With respect to spaces at the end of lines: From a code hygiene perspective, there is no good argument for keeping them. If you are arguing that there is no one in your organization with the programming skill to remove them, then it seems your organization is suffering from problems that JSLint cannot help you solve.
10. If you have a Java mentality, they might be useful. I have a JavaScript mentality.
11. It is much harder to write correct programs if you do not understand what the language actually does.