Before this change, it was always disabling JSLint before each performance test. I thought this was done so that JSLint wouldn't interfere with the results, since it could start running when changing/saving files. What this does now is disable it if it was enable and if the extension was loaded. The first if is just in case some user decides to remove the extensions (maybe they use another JSLint/JSHint extension, and don't want to have this extension) and still wants to run the tests. Even if it is an extension on the default folder, now is possible to easily remove it or move it to samples.