mayoff

34 ms·

361.
by mayoff 15y ago
The suit is back!
362.
by mayoff 15y ago
Facebook is not a startup.
363.
by mayoff 15y ago
The sheets could have simply been stolen.
364.
by mayoff 15y ago
Not actually released by NASA. But still very nifty.
365.
by mayoff 15y ago
Of course you can set N to 1. That's not the same as making the hash table size equal to the number of resources.
366.
by mayoff 15y ago
So instead of locking one mutex to access a resource, you're locking N, so you're N times more likely to have mutex contention. Better let N=1.
367.
by mayoff 15y ago
When will they enhance it to flag the other error in this line: long kMaxDiskSpace = 10 << 30; // Thirty gigs ought to be enough for anybody. 10<<30 is ten gigs, not thirty gigs.
368.
by mayoff 16y ago
Wouldn't it be great if articles like this one actually included a useful link, like to the actual 8th Circuit decision, instead of useless internal links? Here's the decision: http://www.ca8.uscourts.gov/cgi-bin/new/getDocs.pl?case_num=..
369.
How to Read a Newspaper, by Walter Cronkite [pdf](assets.mediaspanonline.com)
4 points by mayoff 16y ago|3 comments
370.
by mayoff 16y ago
His while can be written more concisely, I think: Ether :: while: condition do: block { if: condition call then: { block call while: condition do: block } }
371.
Analyzing fuzzy rankings of colleges(bit-player.org)
24 points by mayoff 16y ago|3 comments
372.
by mayoff 16y ago
I mean that things just don't look or act right. Try firing up Quartz Debug (if you have a Mac), setting the UI Resolution scale factor to 2, and restarting some apps. Every app I checked has problems. For example, every app that used a s
373.
by mayoff 16y ago
Desktop monitor resolution is still at ~100dpi because no desktop OS has solved the scalable UI problem satisfactorily. The OSes have some attempts at support for UI scaling, but none works well enough to run all of the popular software de
374.
by mayoff 16y ago
Some of the advice is just plain wrong depending on your target platform. For example, on my iPad, iPhone 3G (not 3GS), and Safari 5.0 (6533.16)/Mac, using createElement/appendChild is consistently faster than using innerHTML. In Chrome 5