oh, and, move the dpad to the face

1) 5 row keyboard (like a G1)
2) .75-1GB RAM (like an N900)
3) 16 or 32 GB storage (like an N900)
4) 4.1" 800x480 screen (like an N810)
5) in addition to USB client for charge/sync, a USB host/otg port
6) micro-DVI-I port
7) more battery
8) wifi tethering app (on non-rooted phones)

Wish this one had their version of Android on it, just like the 5" one.

Blah blah blah.

At this rate, I'll be getting an Entourage eDGe ($500, 10" dual-pane tablet) before a useful Apple Tablet comes out.

Heck, at this rate, I'll be able to upgrade to the MOTO AMP 10 (due in 2011) before an Apple Tablet comes out. (for those who decide to look that up, Moto != Motorola)

OLED? LCD? blah. Give me a PixelQi hybrid LCD/e-paper display.

I'm more interested in seeing what the final feature list will be. I think a web-only platform will fail. Or even web-only + google gears. I think it's going to need some form of local application layer (in the same way that Android has Dalvik apps). It would make the most sense if Chrome OS also runs Dalvik apps, and Java apps (both Java applets and Java applications), but Dalvik makes the most sense. I'd also think it will need support for local media playing (because sometimes you'll want to play media on it if you're, say, on an airplane and can't access the web).

I think if ChromeOS's features include:
1) Fast Boot (like a splashtop),
2) can hand off to other OSes (also like a splashtop, but not limited to Windows as the "other OS" ... specifically, I may want to have it hand off to Ubuntu and/or Android, depending on other device specifics),
3) can properly handle touch screens, multi-touch, and screen rotation (for both tablets and convertible-tablets) (Ubuntu fails at proper screen rotation with a touch screen),
4) can handle hybrid display devices (like the PixelQi hybrid e-paper/LCD screens),
5) has e-reader software (like the ereader.com software released for Android today, and hopefully Kindle software),
7) has media software (local music files, local video, local pictures, as well as support for remote streaming apps, like Rhapsody, Pandora, and such ... though, the remote streaming stuff can probably be done through Flash),
6) can run local Dalvik, Java, and/or Python applications,
7) has some planned tablet and/or convertible-tablet netbook devices in the line-up, and
8) possibly has both x86 and ARM support,

then I'll probably be rather interested. But for each of those things that isn't present, I'll be progressively less interested.

Put the wifi back in, put a pixelqi display on it, and put Android on it (and/or Ubuntu, if they work out the screen rotation issue -- ideally, make Android into a fast boot splashtop for it, that can hand off to Ubuntu), and I'll buy it.

It'd be nice to see what the full list of devices is.

A 9" or 10" tablet, with KVM support, pixelqi display, and their version of Android, would be quite nice.

I'm only interested in their phone, though, if it'll have a physical keyboard.

Too bad it doesn't have:

1) dpad instead of trackball
2) physical keyboard
3) 4.1" screen
4) T-Mobile 3G

Then it might be interesting.

I can't think of any good reason than Nokia would buy Palm. A few years ago, yes. Today? no. Palm doesn't have anything (including WebOS) that is more valuable than what Nokia already owns. Not even the user base.

Maemo's first edition?

Maemo's first edition was 3 or 4 years ago. The N900 will be shipping with Maemo _5_.

Nokia shouldn't abandon Maemo in favor of Android. They should incorporate the Android runtimes into Maemo, giving customers the best of both platforms.