It's not yet fall, but that doesn't mean I can't hole up in the basement and watch football all weekend. There's nothing better than the college coverage on CBS in beautiful 1080i. I'm sorry Fox and ABC/ESPN, 720p just doesn't cut it. The only thing I'd add would be the falling leaves and cooler temps of Autumn, then it'd be perfect. Well, it'd be perfect if Jo liked football. I'll manage.
This past week, I got the WebKit submodule building again on Mac in the Chromium tree. That doesn't really sound all that impressive, I mean, building WebKit on Mac isn't that hard right? Well recall we're not building what Apple builds. First there's the V8 JS engine replacing KJS. Next there's the port, graphics, and glue layers that isolate WebCore to render into a bitmap rather than drawing directly to a view. Most importantly there's Chromium's resource loaders which turn WebCore into a pure renderer, funneling all i/o traffic to the Chromium host; WebCore no longer handles it's own networking. Needless to say, there's a lot under the hood that's differs from the WebKit.framework that ships with the OS. Hopefully by the end of next week we'll be tackling only link errors with TestShell.
Parasound, the makers of the Halo A51 5-channel amp I own and have raved about in the past, just announced the Halo C3 pre-amp/processor at CEDIA. I'm quivering with excitement. While I don't have an HDMI set (yet), I'll need something that can handle all the new formats eventually, as well as providing balanced outputs to the amp. The C1/C2 won tremendous acclaim without breaking the bank, and while built on an extensible chassis, Parasound never provided upgrades for them and left them to languish. Hopefully the same will not be true of the C3. List of the Halo C3 should be south of $3500 from CEDIA reports, which for an audiophile-quality pre/pro is amazing.
I want my 32Gb iPhone and I'm not going to stop whining until I get it.
Second episode of 90210 was oddly depressing. They're not the Walshes of old, but they're still dorky.
Make sure you catch Hole In The Wall on Fox. It's mindless fun, though I'm not sure if I can take more than a half hour. The regular show is slotted at a full hour.
Two things opened up for me today. First, I'm allowed to talk about my project at Google. Second, it once again involves working directly with the open source community, something I've really enjoyed over the last ten years with Mozilla. I'm talking about the public release of the Chromium project and Google Chrome. To be clear, this is my blog so I'm speaking solely for myself, not for Google. These are all my opinions, and mine alone.
Let's get down to brass tacks: How does this affect Camino? In the short term, it doesn't at all. Plans for Camino 2.0 based on the Gecko 1.9 are underway and unchanged. I have some super-reviews to do for smorgan tomorrow that'll get us closer to 2.0alpha status. There shouldn't be any talk of "doom" or "gloom" because really nothing has changed. People still download Camino and continue to send email to our feedback list saying how much they love the product this community has created. That's just as valid tomorrow as it was yesterday. Camino is a great product and it is appreciated. I'm not just saying that to make myself feel relevant, I want everyone in our community to know their efforts are noticed on a daily basis by real people.
I'm also looking forward to working with and becoming a part of the WebKit community, but more specifically getting jinglepants right back where he belongs. He knows where that is. It's interesting seeing how many people in the Mozilla community also participate in #webkit. I was worried for so long about what I'd say about all this and how it would be perceived and how I'd have to spin it and yadda yadda yadda, but I realized today that it's really just about building great software and being a part of a group of people who want to make the web better, faster, safer, and easier. To move the web forward. It doesn't matter if you're at Google, Apple, Mozilla, or even Microsoft. We're measured by our actions, not our words, so I wanted to make sure I used my experience to help move the needle. I think this new opportunity will allow me to do just that.
My goal (again, speaking for myself) is to build a first-rate, native Mac product for Chromium and make it so that other projects can stand on the shoulders of giants. That's what open source is all about. I don't know why I should be shy about saying that, and I don't feel bad about it one bit.
Stay tuned, I hope to have a lot more to talk about.