Google-api-javascript-client: Where can I get an uncompressed version of https://apis.google.com/js/client.js
_From [email protected] on July 19, 2013 09:56:19_
I'm looking for an uncompressed version of client.js, but I couldn't find it in this repository. I only used the browse feature from google code.
_Original issue: http://code.google.com/p/google-api-javascript-client/issues/detail?id=93_
wonderfly
All 3 comments
_From [email protected] on July 31, 2013 18:11:00_
We do not release source for the JS Client Library.
Status: WontFix
wonderfly
on 7 Jan 2015
any reasons why?
zboralski
on 26 Oct 2015
I'm also curious, echoing @zboralski's question.
It makes it harder to ship open source apps that call Google APIs. It's a standard (and IMHO good) practice for open source apps to provide all javascript from the native server, instead of asking clients to load JS from a third-party server such as https://apis.google.com/.
You can ship jquery and whatnot with your app's code, and arrange for the client side to load all that stuff directly from your app's own server... But then you run into these minified Google Javascript files, and it's not even clear what copyright terms they're under (they don't say). Do you ship them with your own app, risking copyright infringement and risking making your app not fully open source?
Or do you have your code direct client-side users to download it from Google into their own browsers, thus creating a load-time dependency on https://apis.google.com/'s SLA, and, incidentally, exposing your users to some unknown copyright infringement risk themselves?
I understand that Google is under no obligation to release any of this code under an open source license. However, I hope Google will do so, because the current situation is rather hostile to open source applications that call Google APIs.
kfogel
on 14 Jul 2016
Related issues
wonderfly
路
5Comments
futuro
路
7Comments
caesarsol
路
6Comments
nmquaan-bigbom
路
7Comments
dotproto
路
4Comments
Most helpful comment
I'm also curious, echoing @zboralski's question.
It makes it harder to ship open source apps that call Google APIs. It's a standard (and IMHO good) practice for open source apps to provide all javascript from the native server, instead of asking clients to load JS from a third-party server such as https://apis.google.com/.
You can ship jquery and whatnot with your app's code, and arrange for the client side to load all that stuff directly from your app's own server... But then you run into these minified Google Javascript files, and it's not even clear what copyright terms they're under (they don't say). Do you ship them with your own app, risking copyright infringement and risking making your app not fully open source?
Or do you have your code direct client-side users to download it from Google into their own browsers, thus creating a load-time dependency on https://apis.google.com/'s SLA, and, incidentally, exposing your users to some unknown copyright infringement risk themselves?
I understand that Google is under no obligation to release any of this code under an open source license. However, I hope Google will do so, because the current situation is rather hostile to open source applications that call Google APIs.