j_b_f

A pretty good write-up about what went wrong. I like the mitigation procedure of implementing recovery drills that "include the rare and complicated procedures"... whoever runs that is going to have a wickedly fun job!

I have no idea what this guy is talking about.

I've never actually seen Larry Ellison speak before. He's pretty hilarious.

The speaker argues that your memory of an event is based largely on the end of the event itself (such as the pain at the very end of a colonoscopy). Hilariously, the end of the speech itself ends strong but then there's a crappy question-and-answer session at the end that sort of ruins it. Or my memory of it, at least!

Too bad Google isn't marketing or branding these devices. If your strategy as a vendor is "hope our OS provider's branding sort of rubs off on us" I think you need a different approach.

Also, does anyone else hate killer/doomed/war linkbait as much as I do?

Related Sivers article: http://sivers.org/trust-but-verify

Joel's early writing really gave us a solid model for building our company 9 years ago (for better or for worse) and inspired us to start the thing in the first place. For that I will always be grateful.

That was already true for what they're now calling "Windows Phone Classic."

The Microsoft and Linux search "special" searches definitely predate the CSE product. Not sure how long they've been around for, but they're really, really old.

Weird, that blog post reads just like a Steve Jobs keynote, albeit a pretty unimpressive one.

I'll believe it when I see it (that said, I really hope to see it).

Yeah, it's a little over the top. I don't like how articles like this always fail to put forward the theory that maybe Google did the N1 to avoid Windows Mobile's fate by creating an in-production reference platform that commits them to backwards compatibility. It probably won't prevent further fragmentation, but it's worth a shot.

Also, it's not Google's fault that the other Android devices suck ass.

Wow, that's actually great. Thanks for the info.

This page http://www.google.com/adwords/tvads/how.html seems to indicate that the maximum video upload size is 100MB. This seems awfully small for broadcast-quality video. I guess it's only 30 seconds or so, but still.

I'm having the same issue on Chrome/Mac 4.0.249.49.

I'm sure the Flash widgets he's demoing have nothing to do with how his battery is close to dead throughout the demo.

Okay, yeah, you're right. But the takeaway is that while the two American networks are incompatible both the N1 and the iPhone should support world roaming equally well.

If you type fast enough you'll often be pressing the second key with your other thumb before the first thumb has quite left the keyboard. The iPhone allows for this but the N1 doesn't (or doesn't appear to in limited testing).

Not in my experience. Hold down one key, then hit another, the second key doesn't register (like it does on the iPhone).

Sure, I get that. But the description above should suffice for most people. It's the same terminology used by the GSM Association: http://www.gsmworld.com/roaming/gsminfo/index.shtml (this link is awesome in that it shows you what bands the different carriers use for various services)

I've been playing with the Nexus One pretty heavily for the past 24 hours and I can confirm that the battery is basically what you'd expect. Heavy usage means you won't make it through the day, but you can easily do so on reasonable web surfing/texting and moderate numbers of phone calls.

I can confirm this. Stuck my AT&T SIM in my N1 and no 3G. Here's the deal:

Most of the world = 3G 2100, AT&T = 3G 850/1900, T-Mo USA = 3G 1700/2100 MHz, Nexus One = 3G 900/1700/2100. (For reference, iPhone 3G = 3G 850/1900/2100).

I have a Nexus One and I have to say I've quickly become ALMOST as good at typing as I was on the iPhone. Sometimes the lack of multi-touch (pressing one key while you're letting up on another) bites you in the ass but it's pretty rare.

My primary issue with the keyboard is that it's very close to the four un-beveled buttons below the screen. I'll quite often hit "back" when I mean to hit "?123" which is pretty annoying.

I've also had good success with the new voice recognition feature for short emails and text messages.

Overall the keyboard is much less polished than the iPhone but I was pleasantly surprised at how usable it was.

I heard that T-Mo just got their 3G up and running in HNL. Great device to test it out on!

There's inspiration everywhere.

Also, where I live, the Zipcars started to get really beat up and were generally in terrible shape (see my other comment). If you reported every scratch, dent, and problem you'd be calling in every car you rented.

I used Zipcar for a couple of years but in the end found it too inconvenient for my use case (lots of high-mileage multi-day trips). Since I hate traditional car rental places as much as the author I ended up just getting a car, which has been considerably more expensive (but also more convenient) than the old Zipcar.

Near the end of my time with them, I really felt Zipcar was trying to reduce costs... the cars started getting older, they were poorly maintained, and as the service increased in popularity there didn't seem to be a commensurate increase in number of cars available. I wonder if this was just my local neighborhood experience or if those sorts of problems are widespread.

That link was pretty interesting! It's weird to think that contingency fee arrangements were banned until relatively recently.

Holy crap. This is a little tongue-and-cheek, but if it inspires even one person to start an airline Boeing will make their money back in no time!

It's just a press release. Marketing != reality.