When hosted locally it would result in 1 less DNS lookup, as well it could reuse an open HTTP connection to fetch the resource.
So many of these discussion points are discussed at https://developers.google.com/speed/docs/best-practices/rtt
However say for content-based sites, the theoretical ideal is that the content should be delivered and usable without the inclusion of fooLib.js (which folks say should even be included as late as just before </body>), so a delay from a CDN would not necessarily cause any apparent "hang". Again this is the ideal and admittedly I've never got it right.
A simple solution would be to just link to a self-hosted version of the lib.
Edit: To clarify - the reason I don't like the above solution is because if the CDN is slow to respond for some reason, you've just wasted a bunch of your user's time before loading your self hosted version.
There's huge merit in that IMO for single-page type applications that have many lib dependencies.
For content-based pages (dunno what to call them, whatever the opposite of single page apps are) the benefits stated by Google/others are more apparent with the CDN with local fallback approach.
this.jQuery||document.write('<script src="js/jquery-1.8.3.min.js"></sc'+'ript>')