As long as we're writing bad code, here's my stab at the code golf version:

  i=0,a={valueOf:_=>++i}

- Omitting the variable statements in non-strict mode creates global (function scoped) variables

- The comma operator evaluates its operands left to right and returns the rightmost operand, the result of which is irrelevant in this case

- The arrow function allows us to omit parenthesis around the function parameters, so any single character variable name works (in this case _)

- The arrow function syntax also allows us to omit the curly braces, and will automatically return the body of the function.

- Automatic Semicolon Injection allows us to omit the trailing ;

GV could never make calls. It is primarily a call forwarding service (with tacked on free SMS and now MMS) which allows you to make calls to numbers in other states with no additional cost and make international calls for a low rate. You still need to go through your phone service; as far as your service is aware, these calls are going to a local number (the area code of your google voice number).

That's true, but deceptive. Google Voice itself can't make calls in the app or website, but Gmail (web only) and Hangouts (web and app) can. They're offered this service for a very long time.

There is a trailing character missing,

https://www.youtube.com/watch?v=H69YH5TnNXI

Whoops! Sorry, my bad! Thanks for catching my mistake!

Try enabling directwrite via about:config

It's looking great! My only gripe is the lack of contrast in the results. I find it a bit harder to parse than before.

The image and video showcase is well thought out. It is digestible and smooth complement to the general search, well done!

If you add a random query string to the end of the url you'll get the latest signature count. You will have to change it each time you want to see the current count.

https://petitions.whitehouse.gov/petition/pardon-edward-snow...

Your overly hateful and antagonizing message is not necessary. Please take another look at the posting guidelines: http://ycombinator.com/newsguidelines.html

The px unit in css is a bit misleading, the measurement doesn't always correspond to the size of the device pixels. From the spec[1]:

"For a CSS device, these dimensions are either anchored by relating the physical units to their physical measurements, or by relating the pixel unit to the reference pixel. For print media and similar high-resolution devices, the anchor unit should be one of the standard physical units (inches, centimeters, etc). For lower-resolution devices, and devices with unusual viewing distances, it is recommended instead that the anchor unit be the pixel unit. For such devices it is recommended that the pixel unit refer to the whole number of device pixels that best approximates the reference pixel."

[1] http://www.w3.org/TR/css3-values/#absolute-lengths

That's a general problem with chrome on windows rendering sites with custom fonts. It doesn't have directwrite, unlike Firefox and IE.

There has been talks of directwrite coming to Chrome for nearly a year now. We have to suffer the poorly hinted fonts looking terrible for a while longer.