This week is the last chance for big companies to make 2010 product announcements before things slow down for the holidays, and Google’s not letting the opportunity pass them by. Yesterday they announced the Google eBookstore (here’s the Android app) and Gingerbread’s flagship handset, the Nexus S, which will be on sale on December 16th. (Nexus One users, the over-the-air Gingerbread update will hit your handset in “the next few weeks.”) Today, Google announced the Chrome Web Store and their ChromeOS prototype netbook, the Cr-48. Being a laptop girl who loves her keyboard and hasn’t personally fallen for the touchscreen tablet craze (no iPad or Galaxy Tab here yet), the Cr-48 is exciting: full-size keyboard, built-in 3G that’s free-to-cheap with reasonable pay-for-what-you-use plans from Verizon so you’re always online, pure webapps (no native apps) and no spinning hard drive. Needless to say, I applied to be a tester in the pilot program. The boldest thing Google asserted at today’s Chrome event: That you can do ANYTHING in a webapp that you can do in a native app. Truthfully I’m dubious–how do you compile code on the web? Is there a web-based Eclipse?–but I’m willing to give it a try. What did you think of the last bits of 2010 Google goodness? There will be much to discuss on tomorrow’s episode of TWiG.
4 Comments
FrightenedByPenguins
Google eBooks keeps giving me a Not Found message is eBooks only compatible with Gingerbread?
Michael C Gorman
I agree about compilation. I work primarily as a web developer, so I’ve been hoping to find an SSH-style webapp for direct server administration (like Webmin, but more CLI-oriented). If there is one, that could be a good way to deal with the compilation issue, too.
daviecounty
I look forward to your tip tonight when I listen to you, Leo and Jeff during TWIG on Google Listen using my Droid Incredible!
basus
There isn’t a web-based Eclipse, but a few months ago the Bespin web-based text editor was hooked up to a headless Eclipse server so you could run compiles on a remote machine and have the results sent back to your browser. Not compiling *in* the browser, but interaction with compile process via the browser