
Second biggest offender is usually Google Analytics.
That's why it's usually interesting to host the JavaScript file, that seldom changes on your webserver, and only have the img that conveys the data retrieved from the foreign host.
JavaScript loading is usually blocking the rendering whereas img loading usually not.
Actually if they are able to route it directly between satellites instead of having to do sat-earth round trips, it reduces the delay from 4, 6 or 8 trips to just 2 plus a little between sats.
Or, Google Programming Language. All of your code should be GPL.
Very nice one... I didn't even see it coming
... As Google Language. And then opensource their development stack, codenamed openGL.
640 kilos actually... but you can always attach some external "weight boosters".
And then wait the 64-nozzle era of space flight...
Actually It seems even permitted by the GPL to a certain extend. In the GPL Certification Program [http://www.fsf.org/licensing/compliancelab.html] this case is explicitely mentionned (5.a), and you only need to explicit the calling workflow (the protocol IMHO) between the non-GPL and GPL parts.
Hmmm... I think you're right, it is quite explicit "remotely through a computer network".
Nothing is mentioned about IPC on the same machine.
So I don't know if it can apply.
Isn't that why the Affero GPL (http://en.wikipedia.org/wiki/Affero_General_Public_License) was created ?
An interesting fact is that terrorists are also like that : they adapt faster to security measures than governments. As Bruce Schneier said[1], it's all about defending against what the terrorists did last time. You shall never underestimate creativity for evasive maneuvers.
[1] http://www.schneier.com/blog/archives/2009/06/fixing_airport.html
And if it breaks, we will finally see this black line on the equator that is on globes...
"What man has done, man can aspire to do." -- Jerry Pournelle, about space flight