Ako forkaju i ostave otvoreno, a kaze da hoce chrome, ali posebno bitno chromium ce postati jos brzi.
Ovo dolje sto planiraju je sve cista petica a ovo su samo manji zahvati...
- Teach WebCore about multi-process history (currently it assumes same-process synchronous History access)
- Delete the Widget tree (a Mac WebKit1 constraint)
- Split WebCore into modules
- Move code to directly using the sandbox Platform API directly instead of WebCore/platform where possible
- Establish a simpler, stricter tree-gardening system that does not require 2 full time engineers per day
- Experiment with moving the DOM into the JS heap
- Increase multicore use (e.g., html parser, style engine, javascript parser)
- Removing obscure parts of the DOM and make backwards incompatible changes to obscure parts of the DOM that benefit performance or remove complexity.
- Use a modern, faster tcmalloc throughout all of Mac chrome
- Experiment with incremental or parallel layout
- Fix memory leaks by removing the ScriptValue/ScriptState abstractions now that there’s only one JavaScript engine.
- Replace WebKitIDL with WebIDL and remove custom JavaScript bindings code
- Bring WebCore up to speed with DOM3 Events / [DOM] UI Events.