Linked by Thom Holwerda on Mon 16th Aug 2010 18:49 UTC
Internet & Networking Not too long ago Adobe started a "We love Apple" campaign, as a response to Apple's continuous negative remarks about the company. With Flash 10.1 slowly but surely appearing on more and more mobile devices, it seems like the company just doesn't care about it any more. Adobe's CEO Shantanu Narayen has said they've "moved on".
Thread beginning with comment 437194
To view parent comment, click here.
To read all comments associated with this story, please click here.
kaiwai
Member since:
2005-07-06

"So good they're over Apple. When will you stop crashing my web experience on OS X? I'm a customer, and I'm calling for it.

Thank goodness I won't get that experience on iOS.


Don't sweat the small stuff. WebKit2 is coming along and will be ready very soon to keep all 3rd party plugins from ever holding the browser hostage or worse crashing it.

And yes, it leap frogs Google's solution.
"

Safari already has OOP already but the problem is that it isn't available on 32bit platforms and even when it is enabled it isn't the silver bullet given that it can still pull down the browser. These are just bandaid solutions which fail to address the elephant in the room.

Reply Parent Score: 2

tyrione Member since:
2005-11-21

"[q]So good they're over Apple. When will you stop crashing my web experience on OS X? I'm a customer, and I'm calling for it.

Thank goodness I won't get that experience on iOS.


Don't sweat the small stuff. WebKit2 is coming along and will be ready very soon to keep all 3rd party plugins from ever holding the browser hostage or worse crashing it.

And yes, it leap frogs Google's solution.
"

Safari already has OOP already but the problem is that it isn't available on 32bit platforms and even when it is enabled it isn't the silver bullet given that it can still pull down the browser. These are just bandaid solutions which fail to address the elephant in the room. [/q]

http://trac.webkit.org/wiki/WebKit2

Internals

There are two key subsystems that support the process division :

* CoreIPC - an abstraction for general message passing, including event handling. The current implementations use mach messages on Mac OS X, and named pipes on Windows.
* DrawingArea - an abstraction for a cross-process drawing area. Multiple drawing strategies are possible, the simplest is just a shared memory bitmap.

There are two other important abstractions, which may be pushed down to WebCore or WTF over time:

* Run Loops
* Work Queues

Current Status

WebKit2 should be considered an early technology demo. It is not yet production quality. But it's possible to try it out and see how it works at this early stage.

How to try it Out

Use build-webkit --webkit2 on Mac OS X or Windows to build everything. WebKit2 will not work with the shipping version of Safari. Because WebKit2 is an incompatible API break, it requires a custom testbed to run it. A basic web browser application suitable for testing WebKit2 will be landed in the near future.

The WebKit2 documentation page hasn't been updated recently. The source has grown extensively to include the Qt port of it, as well.

It's a different bird than Google's approach.

Reply Parent Score: 2

kaiwai Member since:
2005-07-06

http://trac.webkit.org/wiki/WebKit2

Internals

There are two key subsystems that support the process division :

* CoreIPC - an abstraction for general message passing, including event handling. The current implementations use mach messages on Mac OS X, and named pipes on Windows.
* DrawingArea - an abstraction for a cross-process drawing area. Multiple drawing strategies are possible, the simplest is just a shared memory bitmap.

There are two other important abstractions, which may be pushed down to WebCore or WTF over time:

* Run Loops
* Work Queues

Current Status

WebKit2 should be considered an early technology demo. It is not yet production quality. But it's possible to try it out and see how it works at this early stage.

How to try it Out

Use build-webkit --webkit2 on Mac OS X or Windows to build everything. WebKit2 will not work with the shipping version of Safari. Because WebKit2 is an incompatible API break, it requires a custom testbed to run it. A basic web browser application suitable for testing WebKit2 will be landed in the near future.

The WebKit2 documentation page hasn't been updated recently. The source has grown extensively to include the Qt port of it, as well.

It's a different bird than Google's approach.


Thank you for the link; it appears that even if the plugin runs out of process with Webkit1 there is still the ability to tear down the browser due to a a number of other factors that could cause the browser to crash if the plugin crashes. With further process seperation of the Webkit2 stack it should mean a more robust experience - so far from what I have seen there is no way to test it right now. Hopefully within the next year we'll see webkit2 make its way in the form of Safari 6 or something because its one of those features that are really required these days given how dependent a lot of work is on a robust internet experience.

Reply Parent Score: 2