russ

11 ms·

61.
by russ 16y ago
Good point. I'm very curious now about the selector overhead. We do a number of operations across varying intervals. Surely one of the goals behind distributing the timestamp updates is to minimize the time we block this pipeline. That bein
62.
by russ 16y ago
While I don't have any information on the selector performance, here is a snippet of an email @bcherry, the author of the self-updating timestamps, sent on some performance findings: "Unfortunately, as you'd guess, [updating timestamps] is
63.
by russ 16y ago
They're the same, +new Date doing an implicit cast to number. I prefer getTime as well for its clarity.
64.
by russ 16y ago
It is indeed a performance optimization.
65.
by russ 16y ago
The pronounced slowness was primarily due to an upgrade from jQuery 1.4.2 to 1.4.4 (we're going to downgrade). In addition, we're moving from listening to the scroll event to a time-based dispatcher for loading subsequent pages of tweets.
66.
by russ 16y ago
You can imagine attempting to support something like this when the user has scrolled 20 pages worth through a timeline. We could, of course, backfill newer tweets subsequently up to the most recent (taking a minimum of two requests and a ma
67.
by russ 16y ago
I don't have a breakdown with precise numbers for you, but some bloat comes from the fact that we include all of our templates in the phoenix bundle. Some savings could come from fetching certain components and pages on demand, but right no
68.
by russ 16y ago
Update: Apparently there was a regression introduced last week that has exacerbated this problem. Some folks are working on a fix.
69.
by russ 16y ago
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 ins
70.
by russ 16y ago
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.
71.
by russ 16y ago
Try http://mobile.twitter.com
72.
by russ 16y ago
Over time, NewTwitter does incur a large memory footprint. I've been traveling for a month and haven't looked into the problem in depth, but I'd bet the major culprit is our aggressive caching techniques. It's also worth investigating the n
73.
by russ 16y ago
This is the intention, but there are probably some limits that we could afford to refine. As people switch over, we're starting to get some good data around usage patterns and will certainly tweak if necessary.
74.
by russ 16y ago
#newtwitter is now an API client. Like any other client, we are subject to rate-limits. The fact that the JavaScript API upon which #newtwitter is built can make authenticated, fully client-side API calls, rate limits are necessary.
75.
by russ 17y ago
You also ripped off github's desgin ;-)
76.
by russ 17y ago
except it's 4 characters =P
77.
by russ 18y ago
The Facebook app seems to use this method to display Post/Cancel buttons in a view above the keyboard when leaving comments
78.
by russ 18y ago
We were also rejected the first time as well. And were accepted for a different idea in the next batch.
79.
by russ 18y ago
In case you are interested in the other questionable contents of that directory: http://66.218.69.11/search/cache?ei=UTF-8&p=kpcb.sql&#38...
80.
by russ 18y ago
I'm saving my $75 for HotGirlInYourShirt.
81.
by russ 18y ago
there are lots of inaccuracies in there...
82.
23andMe named Invention of the Year by Time(time.com)
36 points by russ 18y ago|20 comments
83.
by russ 18y ago
fuckingnda.com
84.
by russ 18y ago
We have been officially licensed by CA for maybe 3-4 weeks now. http://www.nytimes.com/2008/08/20/business/20gene.html?_r=2&... A lot changes in a few months ;-)
85.
by russ 18y ago
Go Drew & Arash!
86.
by russ 18y ago
Heh, no. I'm an SE @ 23andMe. http://www.linkedin.com/pub/1/016/160
87.
by russ 18y ago
Not sure all personalized genetics companies are created equal. You seem to be pretty misinformed about what we do. * We indeed do conduct our own research and are currently collaborating with some prominent research institutions (Parkinso
88.
by russ 18y ago
To address some of the things you mentioned: - as we add more people to our database (including Asians), we can make new discoveries relevant to particular genetic groups - GINA prohibits employers/insurers from discriminating against you b
89.
by russ 18y ago
We are officially licensed in California, NY is still pending.
90.
23andMe makes personalized genetics more affordable(23andme.com)
15 points by russ 18y ago|15 comments

More ›