Yeah, we've certainly done it before. `require.js` has better ways of passing in config if/when we move to that, or if we go with `browserify` or something I'm sure there are better things to do as well.

BUT!

This is probably the wrong file for this to be in. `social-media.js` does wacky hot-loading of the social media buttons on the portfolio pages so they can't track a user until the user has clicked on things and asked to be tracked, essentially. Loading the Facebook SDK on script load sort of seems to defeat the purpose of that. We should probably keep the two separate and only load the Facebook SDK where absolutely needed.