Comparison of browser engines

From Wikipedia, the free encyclopedia
  (Redirected from Comparison of web browser engines)
Jump to navigation Jump to search

This article provides general information for browser engines, especially actively-developed ones.[a]

Some of these engines have shared origins.[1] For example, the WebKit engine was created by forking the KHTML engine in 2001.[2] Then, in 2013, a modified version of WebKit was officially forked as the Blink engine.[3]

General information[edit]

Engine Status[a] Steward License Embedded in
WebKit Active Apple GNU LGPL, BSD-style Safari browser, plus all browsers for iOS[4]
Blink Active Google GNU LGPL, BSD-style Google Chrome and all other Chromium-based browsers, notably Microsoft Edge, Vivaldi and Opera
Gecko Active Mozilla Mozilla Public Firefox browser and Thunderbird email client
Goanna Active M. C. Straver[5] Mozilla Public Pale Moon and Basilisk browsers, K-Meleon browser beginning with version 76.2G
Flow Active Ekioh[6] Proprietary Flow browser[7]
Trident[b] Maintained Microsoft Proprietary Internet Explorer browser
EdgeHTML Maintained Microsoft Proprietary UWP apps; formerly in the Edge browser[9]
KHTML Maintained KDE GNU LGPL Konqueror browser
Servo Maintained Linux Foundation Mozilla Public experimental browsers[10][11]
NetSurf[c] Maintained hobbyists[13] GNU GPLv2 NetSurf browser[14]
Presto Discontinued Opera Proprietary formerly in the Opera browser

Operating system support[edit]

The operating systems that actively-developed engines can run on without emulation.

Engine Windows macOS iOS[4] Android Linux BSD
WebKit Yes Yes Yes Yes Yes Yes
Blink Yes Yes No Yes Yes Yes
Gecko Yes Yes No Yes Yes Yes
Goanna Yes No[15] No No[16] Yes Yes
Flow[7] Yes Yes No Yes Yes No

See also[edit]

Notes[edit]

  1. ^ a b Active status means that new Web standards continue to be added to the engine. However, Maintained status can be as minimal as ensuring the engine code still compiles. Discontinued is when the engine code is abandoned.
  2. ^ Internet Explorer continues to receive security updates,[8] which means Trident is still maintained.
  3. ^ NetSurf does not support HTML5 or other recent Web standards,[12] which means it cannot work properly at YouTube, Gmail, and many other popular websites. Thus it does not merit Active status per this article's criteria.

References[edit]

  1. ^ Limer, Eric (2015-07-29). "Can Microsoft Edge Start the Browser War We So Desperately Need?". Popular Mechanics. Retrieved 2016-01-07.
  2. ^ Paul Festa (2003-01-14). "Apple snub stings Mozilla". CNET Networks. Archived from the original on 2009-09-06. Retrieved 2017-02-16.
  3. ^ Bright, Peter (April 3, 2013). "Google going its own way, forking WebKit rendering engine". Ars Technica. Conde Nast. Retrieved March 9, 2017.
  4. ^ a b "Open-sourcing Chrome on iOS!". 2017. Retrieved 26 April 2021.
  5. ^ M. C. Straver. "About Moonchild Productions". Archived from the original on 2017-03-13. Retrieved 2018-04-19.
  6. ^ "About Ekioh". Ekioh.
  7. ^ a b "Flow Browser". Ekioh.
  8. ^ "Lifecycle FAQ – Internet Explorer and Microsoft Edge – Microsoft Lifecycle". docs.microsoft.com. Retrieved August 30, 2020.
  9. ^ Mackie, Kurt (10 December 2018). "Microsoft Edge Browser To Get New Rendering Engine but EdgeHTML Continues". Redmond Mag. Retrieved 21 December 2019.
  10. ^ "A new browser for Magic Leap". 2018-12-03. Retrieved 2019-05-20.
  11. ^ "Firefox Reality for HoloLens 2". 2020-05-21. Retrieved 2020-07-17.
  12. ^ "Development Progress". NetSurf. Retrieved 3 May 2021.
  13. ^ "NetSurf Developer page". Netsurf-browser.org. Retrieved 7 February 2019.
  14. ^ "NetSurf web browser homepage". Netsurf-browser.org. Retrieved 7 February 2019.
  15. ^ "Remove support for MacOS". repo.palemoon.org. Retrieved 4 May 2021.
  16. ^ "Pale Moon for Android is dead". forum.palemoon.org. April 2019. Retrieved 4 May 2021.