try { setTimeout(foo, 1000) } catch (ex) { ... }
won't be caught here if foo throws. In some DOM APIs there are 'onerror' handlers (like XHR), in NodeJS the convention is to have an "error" first parameter in the callback (which is null if there's no error).
Also try-catch generates additional scope object inside the catch clause hence it's a bit more expensive than just doing a function call.
Generally try-catch makes sense in JavaScript only locally when executing some external synchronous code that is known to throw exceptions.
Reminds me of when I was trying to write a Win8/Metro app for fun. Turns out in the particular network class I was using 404's throw exceptions. What a horrific design - 404 isn't an unexpected state at all, particularly when calling restful apis. But there we were, a pointless try/catch or nothing.
A lot of the brokenness with exceptions is software that models expected operational state as exceptions.
Of course, you should be judicious in your usage of try/catch, since it's obviously something that can be abused very poorly.