Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New Twitter Has Become Browser Poison

mikecanex.wordpress.com

Post reply on HN
Print view View original

61–70 of 108 posts

Re: New Twitter Has Become Browser Poison

#61

Post by 1337p337 »

russ wrote: post #27
kragen wrote: post #25

Earlier quoted context omitted.

It also doesn't work in the version of Arora I have. I imagine it will suck as much as Facebook does on the Kindle browser. Is there a version of Twitter that will work in a plain HTML browser with cookies and no JS? Please?

Try http://mobile.twitter.com

As much as I love the minimal UI, the mobile version is crippled by comparison. If they flesh out the features (which can be done without bloating it) or they deprecate the old UI like they're threatening, then I'll use it constantly.

The old UI works great and does not monopolize CPU, unlike the new one which, on load, eats 100% of one core on whatever machine I'm using (to say nothing of the really wide horizontal resolution required).

Re: New Twitter Has Become Browser Poison

#62

Post by Semiapies »

mikecane wrote: post #57
Semiapies wrote: post #37

I can't help thinking that the tacked-on whine about this is why people want iPads and not PCs would make more sense if this post were not about a web-app that would probably slow down any tablet it was accessed on.

The "the tacked-on whine" as you call it was referring to having to check for the latest version of this that and the other bloody plug-in. Point being, people just Want Shit To Work.

Yes, they do...and then they want it to do the Snazzy New Thing that didn't even exist when the thing was built (and integrate with the Wonderful Service and the other Hot Newness).

These are the two omnipresent and conflicting goals that people want out of any computer that's even vaguely general-purpose. Wait long enough, and you'll see it happen on iPads, too.

ETA: I mean, Hell, we're talking about a page in a web browser. This is an example of both the idea of doing everything simply in a self-contained way that Just Works with no fuss...and the post-1994 reality that people want to make web pages do everything, including building applications out of them and live-updating information. And that's even without involving browser plug-ins.

Re: New Twitter Has Become Browser Poison

#64

Post by 1337p337 »

ComputerGuru wrote: post #13
epi0Bauqu wrote: post #10

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/fire…

Firefox's memory leaks are mostly due to JS. On the other hand, if you read the article, you'll notice that the problem is cross-browser.

Re: New Twitter Has Become Browser Poison

#68

Post by russ »

mikecane wrote: post #59

The point of my post is also this: Something changed in the behavior of New Twitter. None of this happened when I was first given access to NT months ago. The problems seemed to crop up simulataneously -- coincidentally -- with my moving to Opera 11 beta. The problems have since spread to all 3 of the browsers I wound up cycling through. So I think Twitter changed something on their end and are unaware of the ripple…

Currently, we're not live streaming. We poll every 30 seconds when focused and fall back to 90 seconds unfocused. When we do push, we'll be using User Streams (http://dev.twitter.com/pages/user_streams) with either Websockets or Flash. Performance should improve when that happens. There are also some other neat tricks we'll be able to do to make the site even faster.

Re: New Twitter Has Become Browser Poison

#69

Post by kragen »

russ wrote: post #27
kragen wrote: post #25

Earlier quoted context omitted.

It also doesn't work in the version of Arora I have. I imagine it will suck as much as Facebook does on the Kindle browser. Is there a version of Twitter that will work in a plain HTML browser with cookies and no JS? Please?

Try http://mobile.twitter.com

Yeah, I've been using it today. I want to love it but I can't. No DM count on the screen (to save three bytes?!), no user icons, no way to tell that I've gone over 140 characters.

Re: New Twitter Has Become Browser Poison

#70

Post by russ »

twodayslate wrote: post #66

New Twitter has a login popup everytime I open it. I am already logged in. I can close this popup and my twitter experience is not effected. Why is this thing even there?

Is the popup a HTTP Basic Auth window? If so, are you using Firefox? This is a ridiculously elusive bug that a couple of us have been trying to diagnose. It appears to be buried in the FF implementation of XHR when a reference to an XHR instance is shared across iFrames. We're working on it.
Post reply on HN