I don't want versions of the web. That's the whole point of the web.
HTML5 is still very much the wild west. Browser specific versions of a site have been common ever since there was more than one browser.
Unless you want everyone to just code their UI to the lowest common denominator, in which case, the whole web would look like geocities circa 1998.
The Chrome label on this NYT app is merely promotional as they were launch partners.
Using just -webkit prefixes everywhere will make sure it just plays nicely with webkit, and not with IE, Opera or Firefox.
Save bandwidth, load time.
To scroll I have to go to the bottom of the page and click on the little arrow. Go to the other side if I want to go back.
The mouse solved that problem last millenia with the scroll wheel. Anywhere on the page, if I decide to scroll, it will scroll, right there, without moving the pointer or my eyes. Simple huh?.
If I want to scroll, just let me scroll. Don't impose restrictions on me.
up/down -- Change section
left/right -- go to next page
tab -- cycle through articles
Actually, now that I try using the keyboard, it's a lot faster than the mouse.
That said, I'm not sure how sustainable it is, unless they're planning on turning it into a paid thing. Any significant number of users is going to put a damper on their bottom line because no ads means no ad revenue.
But it's a good start.
Performance isn't awesome, but then again, the flagship NYTimes iOS app hasn't worked for me in weeks (crashes on startup, fails to refresh articles when no other app has connectivity problems, etc.) so I might just give it a shot as a Times UI for a while.
If you copy a paragraph and paste it into TextEdit you can see the same text still in Georgia 13 without broken rendering.
You can use the assistive zoom to see clearly what is going on. (Hold control and "two finger up" on the trackpad, or scroll wheel up if you are that sort.) The color fringe at the edges of the zoomed letters is the subpixel rendering.
Antialiasing is still on. The pixels go through shades of gray at the edges, it is just the subpixel that is off.
EDIT: bug here http://code.google.com/p/chromium/issues/detail?id=46790
Also, is 'chrome' here referring to Chrome OS or the browser?
-- Back button doesn't work. Must click tiny "close" box.
-- Rather than simply scrolling, must paginate with tiny "next" arrow.