Re:New Twitter Has Become Browser Poison
by Locke1689 on Monday January 17, 2011 @06:56PM
(#2113944)
This is the least scientific analysis I think anyone could get away with. Why doesn't the author just profile the Twitter page to see how much time his CPU spends executing Javascript code and how much memory it consumes while running?
[ Parent
| on HN ]
The author mentioned Shockwave. I don't think he's too technical a user.
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.