Pulling features out two days after they’ve launched is the new fail whale. A little less problematic, but still ridiculous. #twitterlists
Half a second delay caused a 20% drop in traffic [on Google]. Half a second delay killed user satisfaction. […]
This conclusion may be surprising — people notice a half second delay? — but we had a similar experience at Amazon.com. In A/B tests, we tried delaying the page in increments of 100 milliseconds and found that even very small delays would result in substantial and costly drops in revenue.
So you pretty much can’t get phone support for anything Google provides, except… their free public DNS service. How is that not fishy?
Working with InDesign was both infuriating and exhilarating; there’s still nothing like the physicality of print. Anyone need a brochure?
In my mind I’m the editor-in-chief of my Google Reader, rewriting or rejecting each story — and that job is awful for my blood pressure.
The CrunchPad story is entirely obvious; it’s just hard to believe Arrington was a corporate lawyer once.
“Publishing pictures of an unfinished product on a blog… is not a recipe for success,” he said — in a videoconference blogged by every site.
There hasn’t been a new GTD application to play with in a while. You wouldn’t have believed that could ever happen.
I am so annoyed by how few blog posts about Chrome for Mac care to mention that it’s Intel-only. I feel old and abandoned.
J’ai des reflux acides à chaque fois que je tombe sur ces pages de Wikipédia France écrites dans le ton d’un exposé de collégien.
UStream Broadcaster makes crappy video on the iPhone 3G, but that’s better than no video at all http://www.ustream.tv/recorded/2846134
Kindle for iPhone available internationally = downloadable first chapters for lots of books. Too bad the mobile Kindle store sucks.
Damnit! Google Reader has been ignoring all of my feed’s digests for a while, because apparently it now discards hash anchors.
After carefully considering the issue, Apple is now allowing applications to use the function UIGetScreenImage() to programmatically capture the current screen contents. […]
A future release of iPhone OS may provide a public API equivalent of this functionality. At such time, all applications using UIGetScreenImage() will be required to adopt the public API.
This annoys me. A lot. Not because I don’t like the idea of issuing derogations for using this or that function from the private API (which I don’t), but because the reason why everyone wants to use UIGetScreenImage is that it’s currently the only way for an application to capture video and process it on the fly (or to capture video at all on anything but an iPhone 3GS). And I don’t really mind stopgap measures per se, but it scares me to see Apple forum moderators addressing the future issue of having to use the upcoming official screen-capture API, rather than the real problem of not being able to access live video capture from the camera sensor… when the UIGetScreenImage produces awful three-frame-per-second 160-pixel video, and apps for a jailbroken iPhone 3G can instead make somewhat fluid, usable video — because they don’t have to use that terribly inefficient workaround of displaying video, capturing the screen, and encoding it themselves, all on a pretty limited CPU.
Sure, just because Apple doesn’t mention an upcoming video streaming API doesn’t mean it isn’t coming, but I can easily see them being content with the access they just opened for capturing screenshots. And, if or when they finally do give developers a direct access to video capture, I can even more easily imagine that they’d still restrict it to the iPhone 3GS.
And it pisses me off because there’s no good reason for that, and because I’m not going to be able to upgrade until next summer at best. (Well, I might be able to, but even if I got a huge contract next week it would be stupid to upgrade my iPhone this late in the product cycle.) I have kitten videos to make!
Oh my, Amazon finally removes items from my wishlist when I buy them for myself. Took them long enough.
A game called Orba is temporarily free on the App Store, and I recommend you give it a download. Simple, but a nice time waster.
It hunts down the fastest DNS servers available for your computer to use. namebench runs a fair and thorough benchmark using your web browser history, tcpdump output, or standardized datasets in order to provide an individualized recommendation.
Interesting idea — if the program surfaced when Google launched its public DNS servers, I missed it. (And, of course, like all the latest software made in Google, it’s Intel-only, godsdamnit.)
On my Mini I get 68 ms on Google’s servers, and 82 ms on my ISP’s (that’s Free). I had wondered if it was quite reasonable to try and use Google’s Public DNS from all the way across the ocean; apparently, it is.