July 2008 Archive
3631.
Which NAS is best? Synology's looks good... (news.cnet.com)
3632.
Search Add-ons :: Firefox Add-ons (addons.mozilla.org)
3633.
RFC: Leaky abstractions for HTTP encoding, and a better high level abstraction. (renesd.blogspot.com)
3634.
How the iPhone App Store will kill iPhone web apps (mashable.com)
3635.
Interview with Alfred V. Aho (techworld.com.au)
3636.
Graphs aren't social (blog.diegodoval.com)
3637.
Four VCs on Evaluating Opportunities (hbswk.hbs.edu)
3638.
Four Free, Offbeat Apps for the Mac (webworkerdaily.com)
3639.
Acting Squirrelly: If SAP could make R/3 easier to use they would do it, right? (pbs.org)
3640.
IPhone 3G (US) Review (engadget.com)
3641.
GridGain in FireFox? (jroller.com)
3642.
The Time Problem of the Internet (enterventure.com)
3643.
Can Google Lengthen Our Attention Span? (discussionleader.hbsp.com)
3644.
The Next Renaissance: A Talk By Douglas Rushkoff (edge.org)
3645.
USDOT donates $500k to create X-Prize for alternative jet fuel (news.cnet.com)
3646.
Google’s iPhone app is really good (blogs.zdnet.com)
3647.
FCC Gets Firm with Comcast (for blocking P2P traffic) (businessweek.com)
3648.
IM: An Opportunity Or A Threat (internetrack.blogspot.com)
3649.
Starting multiple Google Talk instances on Windows (wastedmonkeys.com)
3650.
A Disquisition on Acquisition and Relinquishment (imploder.blogspot.com)
3651.
10 questions that LBS data can answer (blog.outalot.com)
3652.
DVCS and its most vexing merge (yosefk.com)
3653.
The credit crunch meets Fannie Mae and Freddie Mac (bbc.co.uk)
3654.
The Blind-Spot Between High-Level Decision and Low-Level Muscle Movement (michaelgr.com)
3655.
The Issue Of Trust Is With Google, Not Viacom (techcrunch.com)
3656.
Viacom vs. YouTube: Beyond Privacy (law is increasingly siding with rights owners) (businessweek.com)
3657.
IPhoned: a story of shiny new gadgets and lousy customer service (aralbalkan.com)
3658.
Built-to-order Artificial Bones made from metal alloys are coming (michaelgr.com)
3659.
TECO and DDT (catonmat.net)
3660.
How to Think About the "new" Operator with Respect to Unit Testing (googletesting.blogspot.com)