Can someone explain the google js homepage?

Question

Below are some “weird” snippets found on the Google homepage. (google.com/ncr).

({"s":{"#":[{"h":"ad","g":["Google","E4hE342CDKOgAFYm15AW","1",0,0,1]},{"h":"p","g":["ghead"," ,0]},{"h":"p","g":["footer"," ",0]},{"h":"p","g":["body"," ",0]},{"h":"p","g":["xjsi"," 

And there:

 <script>if(google.y)google.y.first=[];if(google.y)google.y.first=[];if(!google.xjs){google.dstr=[];google.rein=[];window.setTimeout(function(){var a=document.createElement(\"script\");a.src=\"/extern_js/f/CgJlbiswCjhMQAgsKzAOOAosKzAWOBQsKzAXOAQsKzAYOAQsKzAZOA0sKzAdOBssKzAhOCtAASwrMCU4yYgBLCswJjgILCswJzgCLCswKjgCLCswKzgJLCswPDgCLCswQDgFLCswRDgALCswRTgALA/JqRMsHQD1vo.js\";(document.getElementById(\"xjsd\")||document.body).appendChild(a);if(google.timers&&google.timers.load.t)google.timers.load.t.xjsls=(new Date).getTime();},0);\u000agoogle.xjs=1};google.y.first.push(function(){google.ac.m=1;google.ac.b=true;google.ac.i(document.f,document.fq,'','','OvaKevzR5YKoeJu2mSddyQ');(function(){\u000avar a=window.google.f={};af=1;as=1;aa=(new Date).getTime();google.rein.push(function(){af=1;as=1;aa=(new Date).getTime()});google.dstr.push(function(){google.fade=null});function m(b,g,e,f){var d,c=[],i=[];for(var h=0,k;k=b[h++];){var l=document.getElementById(k);if(l)c.push(l)}for(var h=0,j;j=g[h++];){var o=n(j[0],j[1]);while(d=o.pop())c.push(d)}while(d=c.pop())i.push([d,\"opacity\",e,f,0,\"\"]);return i}function n(b,\u000ag){var e=[];for(var f=document.getElementsByTagName(b),d=0,c=f[d];c=f[d++];)if(c.className==g)e.push(c);return e}google.fade=function(b){b=b||window.event;var g=1;if(b&&b.type==\"mousemove\"){var e=b.clientX,f=b.clientY;g=ax||ay?Math.abs(ax-e)+Math.abs(ay-f):0;ax=e;ay=f}var d=(new Date).getTime(),c=da.a;if(google.fx&&g&&c>602)if(af){af=0;var i=[\"fctr\",\"ghead\",\u000a\"pmocntr\",\"sbl\",\"tba\",\"tbe\"],h=[[\"span\",\"fade\"],[\"div\",\"gbh\"]];google.fx.animate(602,m(i,h,0,1))}};\u000a})();\u000a});if(google.j&&google.j.en&&google.j.xi){window.setTimeout(google.j.xi,0);google.fade=null;}</script>",0]},{"h":"zz","g":[0,1]}]},"c":{"1":{"cc":[],"co":["ghead","body","footer","xjsi"],"pc":[],"nb":0,"css":"td{line-height:.8em;}.gac_m td{line-height:17px;}form{margin-bottom:20px;}body,td,a,p,.h{font-family:arial,sans-serif}.h{color:#36c;font-size:20px}.q{color:#00c}.ts td{padding:0}.ts{border-collapse:collapse}em{font-weight:bold;font-style:normal}.lst{font:17px arial,sans-serif;margin-bottom:.2em;vertical-align:bottom;}input{font-family:inherit}.lsb,.gac_sb{font-size:15px;height:1.85em!important;margin:.2em;}#fctr,#ghead,#pmocntr,#sbl,#tba,#tbe,.fade{opacity:0;}#fctr,#ghead,#pmocntr,#sbl,#tba,#tbe,.fade{background:#fff;}#gbar{float:left;height:22px}.gbh,.gbd{border-top:1px solid #c9d7f1;font-size:1px}.gbh{height:0;position:absolute;top:24px;width:100%}#gbs,.gbm{background:#fff;left:0;position:absolute;text-align:left;visibility:hidden;z-index:1000}.gbm{border:1px solid;border-color:#c9d7f1 #36c #36c #a2bae7;z-index:1001}#guser{padding-bottom:7px !important;text-align:right}#gbar,#guser{font-size:13px;padding-top:1px !important}.gb1,.gb3,.gb3i,.gb3f{zoom:1;margin-right:.5em}.gb2,.gb2i,.gb2f{display:block;padding:.2em .5em}a.gb1,a.gb2,a.gb3,a.gb4{color:#00c !important}.gb2,.gb2i,.gb2f,.gb3,.gb3i,.gb3f{text-decoration:none}a.gb2:hover{background:#36c;color:#fff !important}","main":"<div id=ghead></div><span id=body></span><span id=footer></span><span id=xjsi></span>"}}}) 

Here is very interesting:

 onload=\"window.lol&&lol()\" 

Why do they shun everything?

This seems pretty straightforward:

 onblur=\"google&&google.fade&&google.fade()\" 

Appreciate it if you can explain all this. Thanks!

Answer 1

Early examples are basically minimized (removing spaces, using short variable names, etc.) to reduce page size.

Concerning:

 onload=\"window.lol&&lol()\" 

Actually the page:

 onload="window.lol&&lol()" 

He has & , because & must be represented this way in HTML (with the exception of CDATA blocks whose attribute values ​​never exist). So this means:

 window.lol && lol(); 

which means:

If the window object has a property called lol , execute this property as a function.

Using an explicit window object in the first instance is to stop its error if the property is not defined, and the absence of using it in the second instance is to reduce the page size (since window implied when calling a function that is clearly not a method of another object).

Answer 2

I cannot give a complete answer, but infinite acceleration should probably serve older browsers with incorrect character set support.

The reason, of course, is that it is so compressed that it loads very quickly.

edit: I would not call the code unscientific, as it is extremely optimized.

Answer 3

This is probably not the tool used for the Google homepage, but the google closure compiler can cause this type of gibberish.