If anyone still needs convincing these CDN'd JS lib are a bad design pattern, check out this presentation from 2012's Black Hat (and also DEFCON) on MITM attacks on them that persist after the user has been exposed (due to indefinite caching of poisoned JS files).<p><a href="http://media.blackhat.com/bh-us-12/Briefings/Alonso/BH_US_12_Alonso_Owning_Bad_Guys_WP.pdf" rel="nofollow">http://media.blackhat.com/bh-us-12/Briefings/Alonso/BH_US_12...</a>, or
<a href="https://www.youtube.com/watch?v=ZCNZJ_7f0Hk" rel="nofollow">https://www.youtube.com/watch?v=ZCNZJ_7f0Hk</a> (quite entertaining presentation)<p><i>the tl:dr is users browse a short time via an anonymous proxy (c'mon, many do), the proxy MITM's these CDN's JS lib requests and serves up poisoned versions that work but also check a mothership server to load in further poisoned + persistently cached JS files for popular websites (banking, facebook, etc). User then ends their proxy session but future visits (even direct, not via proxy) to sites loads in the now cached poisoned JS libs. Phishing, credential theft, clipboard theft, etc is all now possible</i>