Personally, I steer clear of google api's or frameworks, I prefer to write what I need.
If you want to produce a website with bells and whistles, then knck yourself out, however, you sould be aware of the load you put on a users connection having load a file each page, if your scripting is bespoke to your site and only contains what your site needs, your payload is less, you know what goes in to your page and how to fix things.
Wit ha framework, you rely on others code and for that code to work as expected, the only good thing I can say about frameworks is that they are designed to be cross browser compatible. That again is something I believe shouldn't happen, W3C set the standard and it is then up to browser developers to tow the line, they don't and prefer instead to go off and do their own thing because they think that they know better when the compliance issues are all created because none of them, microsoft included fails to stick to what W3C have set as the standard.
In a perfect works, one script would work in all browsers and you wouldn't need to crawl up your own rear to get your site and code working. HTML was originally designed to be readable even if an error occurs on a page, these days that is just not possible with browser manufacturers having hissy fits over what they want to do and not what they are told to do.