4 ms·

And then there were three. Which will happen first, the death of one of (WebKit, Gecko, Trident) or a new popular rendering engine not related to any of them?

by spicyj 14y ago

kibwen 14y ago
High hopes for Servo[1], but it'll still be years yet until it's able to challenge any of those three. Webkit2[2] will probably be ready sooner, but it's less of a radical departure than Servo's intended to be. [1] https://github.com/mozilla/servo https://github.com/mozilla/servo [2] http://trac.webkit.org/wiki/WebKit2 http://trac.webkit.org/wiki/WebKit2
- bdash 14y ago
  WebKit2 is a new API layer on top of WebKit, not a new browser engine. It has been used by Safari since v5.1.
  - kibwen 14y ago
    Are you sure about that? When I read quotes like "web content (JavaScript, HTML, layout, etc) lives in a separate process from the application UI", that conjures images of a rather drastic and fundamental change. I'm not sure how you'd achieve that with just a new API layer.
    - bdash 14y ago
      Yes, I'm sure. The same core rendering engine, known as WebCore, is shared between both WebKit1 and WebKit2 on OS X. WebKit1 is used by most applications that use a WebView to display web content, while WebKit2 is used by Safari. The different API layers set up different delegate callbacks for WebCore so that they can tweak the behavior to fit their architecture (single process vs separate web and UI processes).
    - gcp 14y ago
      Firefox for Android does this, and it's not like the underlying Gecko engine is different.
      - khuey 14y ago
        Firefox for Android no longer does this, and hasn't since the "Native Fennec" launch.
        kbrosnan 14y ago
        You two should hug this out in #mobile.
- zobzu 14y ago
  Those project are pretty damn cool. I have a preference for servo just because of it's high coolesness factor. Being in rust and even more modular. Oh yeah also, while I guess it's missing a lot, the code is actually very, very readable. That's nice. https://github.com/mozilla/servo/tree/master/src/servo https://github.com/mozilla/servo/tree/master/src/servo (the actual layout engine part)
- dbcooper 14y ago
  Doesn't Safari already use Webkit2? http://en.wikipedia.org/wiki/Safari_(web_browser)#WebKit2 http://en.wikipedia.org/wiki/Safari_(web_browser)#WebKit2
rythie 14y ago
I'd like to see some serious work done on Dillo ( http://www.dillo.org/ http://www.dillo.org/ ), which is much faster than chrome on low-end boxes and could be really good for developing countries.

And then there were three. Which will happen first, the death of one of (WebKit, Gecko, Trident) or a new popular rendering engine not related to any of them?

by spicyj 14y ago

And then there were three. Which will happen first, the death of one of (WebKit, Gecko, Trident) or a new popular rendering engine not related to any of them?

kibwen 14y ago

High hopes for Servo[1], but it'll still be years yet until it's able to challenge any of those three. Webkit2[2] will probably be ready sooner, but it's less of a radical departure than Servo's intended to be. [1] https://github.com/mozilla/servo https://github.com/mozilla/servo [2] http://trac.webkit.org/wiki/WebKit2 http://trac.webkit.org/wiki/WebKit2

bdash 14y ago
WebKit2 is a new API layer on top of WebKit, not a new browser engine. It has been used by Safari since v5.1.
- kibwen 14y ago
  Are you sure about that? When I read quotes like "web content (JavaScript, HTML, layout, etc) lives in a separate process from the application UI", that conjures images of a rather drastic and fundamental change. I'm not sure how you'd achieve that with just a new API layer.
  - bdash 14y ago
    Yes, I'm sure. The same core rendering engine, known as WebCore, is shared between both WebKit1 and WebKit2 on OS X. WebKit1 is used by most applications that use a WebView to display web content, while WebKit2 is used by Safari. The different API layers set up different delegate callbacks for WebCore so that they can tweak the behavior to fit their architecture (single process vs separate web and UI processes).
  - gcp 14y ago
    Firefox for Android does this, and it's not like the underlying Gecko engine is different.
    - khuey 14y ago
      Firefox for Android no longer does this, and hasn't since the "Native Fennec" launch.
      - kbrosnan 14y ago
        You two should hug this out in #mobile.
zobzu 14y ago
Those project are pretty damn cool. I have a preference for servo just because of it's high coolesness factor. Being in rust and even more modular. Oh yeah also, while I guess it's missing a lot, the code is actually very, very readable. That's nice. https://github.com/mozilla/servo/tree/master/src/servo https://github.com/mozilla/servo/tree/master/src/servo (the actual layout engine part)
dbcooper 14y ago
Doesn't Safari already use Webkit2? http://en.wikipedia.org/wiki/Safari_(web_browser)#WebKit2 http://en.wikipedia.org/wiki/Safari_(web_browser)#WebKit2

rythie 14y ago

I'd like to see some serious work done on Dillo ( http://www.dillo.org/ http://www.dillo.org/ ), which is much faster than chrome on low-end boxes and could be really good for developing countries.