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

91–100 of 108 posts

Re: New Twitter Has Become Browser Poison

#91

Post by mkramlich »

redthrowaway wrote: post #40
riobard wrote: post #33

Earlier quoted context omitted.

Same problem here with Safari. I'll vote for process-per-tab as the single best feature of Chrome.

Me too. The overhead is slightly higher, but having crashes and memory leaks confined to a single tab is awesome.

I left Firefox for Safari because Safari was prettier, faster and used less memory.

Lately, I'm close to leaving Safari for Chrome because it's faster, uses less memory and crashes less (in fact, it's never crashed so far, vs 100's of times total probably with Safari.) Unfortunately, Chrome is a little uglier, and has certain less user conveniences. So it's not an easy jump to make.

Re: New Twitter Has Become Browser Poison

#92

Post by minalecs »

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.

Agree that ipad promotion at the end is not really a fair comparison. I'm assuming he's speaking of the twitter app on the ipad. For it to be fair he should install a desktop client for twitter on his pc or possibly tweetdeck and make a comparison.

Re: New Twitter Has Become Browser Poison

#94

Post by redthrowaway »

mkramlich wrote: post #91
redthrowaway wrote: post #40

Earlier quoted context omitted.

Me too. The overhead is slightly higher, but having crashes and memory leaks confined to a single tab is awesome.

I left Firefox for Safari because Safari was prettier, faster and used less memory. Lately, I'm close to leaving Safari for Chrome because it's faster, uses less memory and crashes less (in fact, it's never crashed so far, vs 100's of times total probably with Safari.) Unfortunately, Chrome is a little uglier, and has certain less user conveniences. So it's not an easy jump to make.

You think Chrome is ugly and inconvenient? I think it's the best looking browser out there, and the omnibox is fantastic. The only thing I don't like about Chrome on OSX is some flash players don't play nice with it.

Re: New Twitter Has Become Browser Poison

#95

Post by mike-cardwell »

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

Trouble with the mobile version is it doesn't support https for some reason and so can't be used safely on an untrusted network. The normal version supports https though...

Re: New Twitter Has Become Browser Poison

#96

Post by sesqu »

redthrowaway wrote: post #40
riobard wrote: post #33

Earlier quoted context omitted.

Same problem here with Safari. I'll vote for process-per-tab as the single best feature of Chrome.

Me too. The overhead is slightly higher, but having crashes and memory leaks confined to a single tab is awesome.

They're not confined to a single tab for me. It seems like child tabs go in the parent process, for example, so I usually get 2-5 tabs crashing at once.

I also get more crashes with Chrome than I used to get with Firefox, but maybe I'm just opening more tabs.

Re: New Twitter Has Become Browser Poison

#97

Post by mikecane »

russ wrote: post #68
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.

But something changed somewhere. Scrolling used to be a smooth experience. The entire use of NT was exciting and not cloggy. Now it is hell scrolling and very cloggy and even autocomplete of IDs is a torment. What did you guys do over there to the code?

Re: New Twitter Has Become Browser Poison

#98

Post by mikecane »

bkudria wrote: post #60
mikecane wrote: post #58

Earlier quoted context omitted.

I dropped Shockwave in there as yet another example of something else that needs to be checked for the latest version. Not every plug-in is good about saying there's an update and most of the time the update notifications come in the middle of getting work done, so people tend to disable that distraction.

Yeah - but New Twitter has absolutely nothing to do with Shockwave.

Yes, I know that. You are taking it too literally, that one little bit. I was simply listing a bunch of updates that techs always ask about having been updated.

Re: New Twitter Has Become Browser Poison

#99

Post by mikecane »

Semiapies wrote: post #62
mikecane wrote: post #57

Earlier quoted context omitted.

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…

Yes, and I do sympathize. This stuff isn't like a light switch that you turn on and have the room all lit up despite whatever changes have been made to the backend with the transmission lines and generators, etc. But sometimes we want it to act that way.
Post reply on HN