For public facing web site/blogs, everyone using the same CDN might make your page load faster because there's a good chance a visitor to your site already load

For public facing web site/blogs, everyone using the same CDN might make your page load faster because there's a good chance a visitor to your site already loaded it from a CDN. So initially I was all for using NetDNA's CDN (they maintain all versions, both css and js). However, over time I revised my opinion. During development, it's usually nicer to have all your static files associated with the project in your project directory. There might also be a situation where you're developing offline (or crappy hotel wifi) and a failed GET just messes up your whole rhythm. Additionally, a lot of my work is internal projects. If I'm throwing together a quick web application, or even just a static site, I use bootstrap's grid, table classes, and icon packs to make that project look nicer. But I felt that for a secure application that can only be reached while on our VPN, it didn't make sense to refer the browser to a piece of javascript running out on the internet. Even if no malicious tracking code is injected into the js, I don't need to give this third party server details like 'REFERRER=https://passwordvault.corp.example.com/?q=jsmith' https://passwordvault.corp.example.com/?q=jsmith'.