[webkit-dev] Handling of feature dependencies
eric at webkit.org
Tue Jan 4 11:47:16 PST 2011
The more you turn off, the less the binary you create is "WebKit". It
tells servers its "WebKit" via its useragent, but then it doesn't have
the features that pages have come to expect from WebKit -- this is bad
for WebKit and bad for your users.
A better course of action is to study the memory usage and reduce
memory usage for all ports of WebKit, instead of just hacking off
lumps. I think you'll find that things like the "console" don't use
much memory at all.
Obviously many "devices" have already shipped with "full" copies of
WebKit. If you have a very low-memory/low-power device (more than a
cell phone or a TV or a car or something that would run Qt -- all of
these have numerous shipping example devices using WebKit), then
WebKit is probably not what you want anyway. :)
On Tue, Jan 4, 2011 at 11:17 AM, Darin Adler <darin at apple.com> wrote:
> On Jan 4, 2011, at 2:59 AM, Konstantin Tokarev wrote:
>> 03.01.2011, 23:58, "Darin Adler" <darin at apple.com>:
>>> On Jan 3, 2011, at 12:53 PM, Konstantin Tokarev wrote:
>>>> I'd like to get WebKit running on device with very limited resources. Basically, it would be quite enough if resulting "browser" just properly displayed HTML 4 + CSS 2.1, and it would be highly desired to reduce size of binaries and memory usage as it's possible
>>> This is a non-goal for the WebKit project. Please look at <http://webkit.org/projects/goals.html>.
>>> I understand that you might want that, but the project doesn’t accommodate everything that everyone wants, especially someone who has not yet contributed something else.
>> OK, but don't you think that some extra shrinking options may be useful for everyone using WebKit in embedded environments?
> I don’t.
> But maybe you could convince me with specific examples.
> -- Darin
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev