3 ms·

Enjoyed the article, but I had to read it using the Clearly extension because the native web page is extremely laggy for me. I'm on a Win8 machine running curre

by Fuzzwah 13y ago

Enjoyed the article, but I had to read it using the Clearly extension because the native web page is extremely laggy for me. I'm on a Win8 machine running current Chrome. It seems like such a simple design but hot damn does it chug when I scroll.

petemc_ 13y ago
Works fine with safari on my 2008 macbook.
KnightHawk3 13y ago
Same on Windows 7 with Chrome (IGP with a Mobile 1st gen i3 processor however)
HNaTTY 13y ago
That's probably because it's a 15MB page including all the assets -- Somebody doesn't believe in jpegs. The page still downloaded for me in 2.5s though, so I have to give the guy some credit for having a beefy host.
- kingnight 13y ago
  I think it may have to do with the fixed 'border' the entire page has. It is interesting though how Chrome chokes and Safari glides, though with choppy repositioning of the fixed border on scroll completion.
rogerchucker 13y ago
Don't wanna start an off-topic conversation but in spite of being somewhat of a Google fanboy I'm actively using (and have set as default) Safari instead of Chrome on my 2010 macbook pro for any page or site that is "heavy". My usage of Chrome has now shrunk to scenarios that involve heavy dependence on omni-search.
JoshuaRedmond 13y ago
I'm glad I wasn't the only person who had that issue. Strangely it works perfectly on the mobile version of Chrome for Android, but it grinds to a halt on the tablet version. This is especially strange as I have a Padfone 2 (phone connects to a tablet dock) , so the hardware is the same, and Chrome just gets relaunched in tablet mode when it's docked. Maybe due to the size of images being served being varied on screen size.
Cyykratahk 13y ago
That would be the 300px radius inner box-shadow set to 5% opacity on the body tag, which happens to be over 40,000px tall.

3 ms·

Enjoyed the article, but I had to read it using the Clearly extension because the native web page is extremely laggy for me. I'm on a Win8 machine running curre

by Fuzzwah 13y ago

petemc_ 13y ago
Works fine with safari on my 2008 macbook.
KnightHawk3 13y ago
Same on Windows 7 with Chrome (IGP with a Mobile 1st gen i3 processor however)
HNaTTY 13y ago
That's probably because it's a 15MB page including all the assets -- Somebody doesn't believe in jpegs. The page still downloaded for me in 2.5s though, so I have to give the guy some credit for having a beefy host.
- kingnight 13y ago
  I think it may have to do with the fixed 'border' the entire page has. It is interesting though how Chrome chokes and Safari glides, though with choppy repositioning of the fixed border on scroll completion.
rogerchucker 13y ago
Don't wanna start an off-topic conversation but in spite of being somewhat of a Google fanboy I'm actively using (and have set as default) Safari instead of Chrome on my 2010 macbook pro for any page or site that is "heavy". My usage of Chrome has now shrunk to scenarios that involve heavy dependence on omni-search.
JoshuaRedmond 13y ago
I'm glad I wasn't the only person who had that issue. Strangely it works perfectly on the mobile version of Chrome for Android, but it grinds to a halt on the tablet version. This is especially strange as I have a Padfone 2 (phone connects to a tablet dock) , so the hardware is the same, and Chrome just gets relaunched in tablet mode when it's docked. Maybe due to the size of images being served being varied on screen size.
Cyykratahk 13y ago
That would be the 300px radius inner box-shadow set to 5% opacity on the body tag, which happens to be over 40,000px tall.