Chrome uses a one-process-per-window model that trades stability/security for memory use and efficiency. That is fine on a desktop with multiple gigs of ram, not so good on an embedded device.
On Fri, Apr 10, 2009 at 9:35 PM, Jesse McGrew <[email protected]> wrote: > > On Apr 10, 3:13 pm, Disconnect <[email protected]> wrote: > > You must run windows. (Not being snarky, but that is the only place > chrome > > runs.. no mac, no linux.) > > > > Android is webkit for a very simple reason - its embeddable. Its small, > it > > has a decent separation of display (java, on android) and core engine (C) > > and in general works small. > > > > Chrome .. doesn't. (By design, in fact, its a memory hog.) So I can't > speak > > for google, but I can say its -very- unlikely, for a lot of reasons. > > Er... Chrome is based on WebKit too. > > Jesse > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
