Wielu z Was pobiera lub już pobrało bety iOS 9 czy OS X 10.11 El Capitan. Fajnie, że możecie czy też chcecie sobie pozwolić na niestabilne OS-y na jedynych sprzętach, a nie dedykowanych do eksperymentów. Chciałbym Wam jednak przypomnieć, żeby czytać … Czytaj dalej
Wprowadzenie do WebKit Content Blockers →
24 czerwca 2015 · 10:51
Benjamin Poulain:
The JavaScript extensions model has been great for many use cases, but there is one category of extensions where members of the WebKit project felt we should do better: the content blocking extensions. Such extensions are the most popular kind; they let users decide what should load and not load, who can track them, what should be visible on pages, etc.
The reason we are unhappy about the JavaScript-based content blocking extensions is they have significant performance drawbacks. The current model uses a lot of energy, reducing battery life, and increases page load time by adding latency for each resource. Certain kinds of extensions also reduce the runtime performance of webpages. Sometimes, they can allocate tremendous amounts of memory, which goes against our efforts to reduce WebKit’s memory footprint.
It is an area were we want to do better. We are working on new tools to enable content blocking at a fraction of the cost.
One new feature, we are developing allows describing content blocking rules in a structured format ahead-of-time, declaratively, rather than running extension-provided code at the moment a decision about blocking needs to be made. This model allows for WebKit to compile the ruleset into a format that’s very efficient to apply to loads and page content.
