I don't think it's deliberately biased, just a guy who's not very invested into the VSCode/Typescript ecosystem who's going back to his known tools.

FYI TSLint still has a large amount of config required to get it working, and the vscode integration still has a "wont-fix, upstream" bug where it won't lint files unless they are open in the editor. So you need to manually run tslint from the commandline. See: https://github.com/Microsoft/vscode-typescript-tslint-plugin...

I'm guessing that webstorm does this this more auto-magically for the user.