On Thu, Nov 6, 2008 at 2:05 PM, Amanda Walker <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 6, 2008 at 4:45 PM, Darin Fisher <[EMAIL PROTECTED]> wrote: > >> It sounds like things are still fairly speculative... > > > Well, performance differences are not speculative, though we don't know > what the effect on Chromium would be. > > Since Linux and Darwin are so similar, it seems like it would be very nice >> to share code. >> > > Linux and Darwin are only superficially similar, and the differences get > larger the closer to the kernel we get. I realize I'm being repetitious > here :-), but generally speaking, starting with the assumption that one > technique will work on both, especially if it involves IPC, threading, or > process creation, is a mistake. While I have some bias from personal > experience, this issue comes up again and again in places like the > darwin-dev mailing list, where "X works fine on my Linux box, why doesn't > work well on the Mac?" might as well be a FAQ. > > I agree that it would be very nice to share code. We have to write a > pipe/socket based implementation for Linux anyway, so I'm not arguing > against that at all. I'm suggesting that we also do a bake-off of that > against native IPC on the Mac, and make a decision based on objective data. > We're talking about a small amount of code, so the benefit of doing so > should greatly outweigh the cost. > > --Amanda > > I don't object to a bake off. It just seemed like we were skipping ahead to just do an OSX-specific solution first, leaving the bake off for later (or never). Did I misunderstand? -Darin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
