[josteink]

From the pictures itself it seems obvious that whoever wrote this suffers from the infamous valley "if it works on my iPhone, it's standard-compliant"-syndrome.

Because, you know, it breaks horribly in most stuff I throw at it and performs horribly bad even on desktop Chrome on a dev-machine.

[d0ugal]

Works fine on desktop Chrome for me.

[lowboy]

Works fine on Chrome stable on my desktop, and on Chrome on my Galaxy SII. Haven't tested other browsers.

[patrickaljord]

It works great here on both ubuntu (xps 13 laptop) and android (Jelly Bean) with the latest chrome.

[josteink]

Still. iPhone (only) tailored web-development has taken the web back into the "this site was designed for MSIE" abyss.

Guessing if things posted on HN will work in browsers and OSes I use (non provided by Apple, for highly ethical reasons) is a daily game of chance.

Is that really what we want? Is that the future we want? Wasn't this what we all shunned Microsoft for doing?

[jasonkostempski]

The difference is that when people build on cutting edge tech that just about everyone agrees will be standard eventually they help push the advancement of that technology, when people built for IE only they used tech just about everyone agreed was horrible, caused vendor lock-in and was a huge security risk. I think if it works on Chrome, Firefox, IE 10, Windows, Linux, Mac, iOS and Android, we're pretty clear of vendor lock-in.

[leeoniya]

working on Fennec (firefox mobile) nightly