>> Secondly, pass your code through a good lint tool to ensure that you've not used any undeclared variables, since undeclared variables will cause implicit global variables. This is also regarded as a general best-practice for JS development, and there's absolutely no reason you shouldn't adhere to it.
"use strict" is a good idea to ensure quality of your code, no doubt. However, the point I was making was about global pollution. Though "use strict" will help in ES5 browsers, a lint is the only comprehensive way to make sure there's no global pollution in older browsers.
Monosyllabic answer is monosyllabic. You only state that you disagree, not why you disagree. Doesn't help take the discussion forward.
>> if you are going to try to come off as an authority
Why would you think I want to do that? I'm sharing my experience and my knowledge, and you are free to take it or discard it. Also, do you think it's better to attack me while making no real argument?
If you have to come across as having a real point, you are going to have to do better than that.
How about 'use strict'