Live data from Hacker News

New Twitter Has Become Browser Poison

mikecanex.wordpress.com

11–20 of 108 posts

Re: New Twitter Has Become Browser Poison

#11
I've experimented with the new twitter web app on both Chrome and Safari (Mac).

It automatically loads a chunk of data when I scroll to the bottom. The CPU use seems to be proportional to the number of chunks that have been loaded. Initially about 2% and increasing to 50% with 20 chunks.

The new twitter almost unusable because of this. Hoping for a fix soon.

Re: New Twitter Has Become Browser Poison

#13

I've been keeping twitter open in its own Firefox browser on one screen (of three). It routinely refreshes itself and there is some kind of memory leak whereas after a day it is consuming about half a gig of memory, forcing me to kill and restart.

Firefox has crazy memory leaks. Don't blame it on twitter, regardless how bad their code may be.

A tab should be completely and utterly destroyed when refreshed. It doesn't matter how much memory it used, refreshing it or navigating away from that page should (ignoring optimizations, caching, etc. etc. etc.) be like you were never there.

Just look at the hundreds of complaints here: http://neosmart.net/blog/2008/firefox-3-is-still-a-memory-ho...

Re: New Twitter Has Become Browser Poison

#14
The thing I noticed in the slow new Twitter is that typing a new status seems to involve continuous autofill-like behavior for each character typed, which seemed to introduce round-trip lag (or javascript-parsing, or...) and causes characters to appear at a rate of ~1/second. Unusable.

And this is one way that dominant sites fall: business considerations are given priority over the user experience. Maybe they just have Flickr-itis and just can't adapt to leaving well enough alone, but for the time being I'm on old-Twitter and not contributing much to the Twitterverse until this is sorted out. If it never winds up being fixed, I've got a head start in living without them.

There is also a possible Second System Effect amongst Twitter's UX gods. It's interesting that after having switched to the new Twitter a couplefew weeks ago, last week I started seeing a "Wanna switch back to the old Twitter?" header. Of course I did, but to me this possibly points to a level of complaints that I did not realize.

Re: New Twitter Has Become Browser Poison

#16
post #9

I noticed the same thing on my girlfriends CR-48, twitter wont scroll properly (studders) and everything else hangs a bit. She filed a bug report with google chrome os support, but I suspect twitter is doing a lot of heavy stuff in the background.

I've noticed the same thing on mine. It seems like the site is only functional when you first load it. After new tweets start rolling in, it becomes worse and worse. I don't think it's the fault of the CR-48, I think we're just seeing the effects worse on this hardware.

Re: New Twitter Has Become Browser Poison

#17
post #9

I noticed the same thing on my girlfriends CR-48, twitter wont scroll properly (studders) and everything else hangs a bit. She filed a bug report with google chrome os support, but I suspect twitter is doing a lot of heavy stuff in the background.

I'll second this. It's by far the worst performing website/app I use on a regular basis on my Cr-48.

Re: New Twitter Has Become Browser Poison

#18
post #9

I noticed the same thing on my girlfriends CR-48, twitter wont scroll properly (studders) and everything else hangs a bit. She filed a bug report with google chrome os support, but I suspect twitter is doing a lot of heavy stuff in the background.

I have this same problem (only recently!) on my 1.6GHz Core Duo laptop. It only started happening recently in new twitter. I'm not sure what's going on but it's almost unresponsive.

Re: New Twitter Has Become Browser Poison

#19
post #9

I noticed the same thing on my girlfriends CR-48, twitter wont scroll properly (studders) and everything else hangs a bit. She filed a bug report with google chrome os support, but I suspect twitter is doing a lot of heavy stuff in the background.

I believe the scrolling issues are tied to their use of position: fixed for the sidebar where that DIV has its own internally scrollable frame via overflow: scroll. The combination of those two are taxing on the browser's overall layout system which causes a dramatic slowdown on less powerful machines. Heck, it's even a little sluggish on my iMac.
Post reply on HN