Wednesday, February 17, 2010

Working on Chrome OS at Google

Many have been curious what I'll be working on at Google, including myself for a while. Google is interesting in that you are not allocated to a team until just before your first day. You accept the job because you're a good fit for Google in general, not just one team.

I'm going to work on Chrome OS. There's a lot to do for the initial launch, but long term my goal is to help make it a great platform for rich graphical apps and games too.

Whoa, you say, I thought you worked on high performance games? Yes, high performance 3D games will be running inside browsers, with security and performance delivered via Native Client.


  1. So what's this mean in relationship to O3D ("an open-source web API for creating rich, interactive 3D applications in the browser", to quote Google's page), if you know? Hard for me to keep track of it all...

  2. O3D is pretty interesting - one of the things that caught my eye to the job in the first place. I've met several engineers who worked on O3D.

    But, there isn't anything I can say about working on Chrome OS and how it relates to O3D.

  3. Schweet. I was trying to ask about this in the mailing list when it was opened, but didn't really get a proper answer. I think somebody casually linked to NaCl though but without any kind of written assurance that it would actually be available in Chrome OS.

    It would be nice to hear as frequent as possible updates in your blog, about the progress regarding this stuff... i.e. how to make well performing games (and demos!) for the platform. :)

  4. ;) Mmm, I still need to learn the blogging policy, but I look forward to sharing as much as I can as soon as I can.

  5. Google thinks they're such hot shit they can't even tell you upfront what you're gonna work on? How Nazi!

  6. I wasn't aware that you had left Emergent. Congratulations on your new gig!