GNOME Web (called Epiphany until 2012) is a free and open-source web browser based on WebKitGTK, developed by GNOME for Unix-like systems. It is the default web browser of GNOME; forked from Galeon in 2002[5], it has since been developed as part of the GNOME Core Applications.

GNOME Web 3.34
Original author(s)Marco Pesenti Gritti
Developer(s)The GNOME Project (mostly by Michael Catanzaro and Xan Lopez, both from Igalia)[1]
Initial release24 December 2002 (2002-12-24)[2]
Stable release(s) [±]
3.34.2[3] (25 November 2019 (2019-11-25)) [±]
Preview release(s) [±]
3.35.2[4] (24 November 2019 (2019-11-24)) [±]
Written inC (GTK)
Operating systemUnix-like
Sizeless than 2 MB (package file, without dependencies)
Available in60 languages
TypeWeb browser

GNOME Web as a component of GNOME Core Applications provide full integration with GNOME settings and components like GNOME Keyring to securely store passwords, following the GNOME Human Interface Guidelines and GNOME stack to providing first-class support for the all new-adopted edge technologies such as Wayland and the latest major GTK versions,[6] multimedia support using GStreamer and small package size (~2MB) due to using shared components;[7] other features include the reader mode,[8] mouse gestures, smart bookmarks, web application integration,[9] built-in ad blocking, and Google Safe Browsing.[10]


Web was originally named "Epiphany", but was rebranded in 2012 as part of GNOME 3.4.[11] The name Epiphany is still used internally for development, such as for bug tracking and in the source code.[12] The package remains epiphany-browser in Debian-based distros[13](to avoid a name collision with a video game that is also called "Epiphany") and epiphany in Fedora-based distros.[14]

Development history

Galeon fork

Marco Pesenti Gritti, the initiator of Galeon, originally developed Epiphany in 2002 as a fork of Galeon. The fork occurred because of the disagreement between Gritti and the rest of Galeon developers about new features. While Gritti regarded Galeon's monolithic design and the number of user-configurable features as factors limiting Galeon's maintainability and usability, the rest of the Galeon developers wanted to add more features.

Around the same time, the GNOME project adopted a set of human interface guidelines, which promoted simplification of user interfaces. As Galeon was oriented towards power users, most developers dissapproved. As a result, Gritti created a new browser based on Galeon, with most of the non-critical features removed. He intended Epiphany to comply with the GNOME HIG. As such, Epiphany used the global GNOME theme and other settings from inception.[5][15]

Gritti explained his motivations:

While Mozilla has an excellent rendering engine, its default XUL-based interface is considered to be overcrowded and bloated. Furthermore, on slower processors even trivial tasks such as pulling down a menu is less than responsive. Epiphany aims to utilize the simplest interface possible for a browser. Keep in mind that simple does not necessarily mean less powerful. We believe the commonly used browsers of today are too big, buggy, and bloated. Epiphany addresses simplicity with a small browser designed for the web—not mail, newsgroups, file management, instant messaging or coffee making. The Unix philosophy is to design small tools that do one thing, and do it well.

Marco Pesenti Gritti[16]

Galeon continued after the fork, but lost momentum due to the remaining developers' failure to keep up with changes in the Mozilla platform. Galeon development stalled and the developers decided to work on extensions to bring Galeon's advanced features to Epiphany.[15]

Epiphany's early philosophy included a commitment to creating a web browser specifically for GNOME:

Epiphany's main goal is to be integrated with the gnome desktop. We don't aim to make Epiphany usable outside Gnome. If someone will like to use it anyway, it's just a plus. For example: Making people happy that don't have control center installed is not a good reason to have mime configuration in Epiphany itself.

Marco Pesenti Gritti[16]

Gritti ended his work on Epiphany and a GNOME team led by Xan Lopez, Christian Persch and Jean-François Rameau now direct the project.[17] Gritti died of cancer on May 23, 2015.[18]


The first version of Epiphany was released on December 24, 2002.[2]

Epiphany initially used the Gecko layout engine from the Mozilla project to display web pages. It provided a GNOME graphical user interface for Gecko, instead of Mozilla's cross-platform interface.[19]

The development of Epiphany was mainly focused on usability improvements compared to major browsers at the time. The most notable was the new text entry widget, which was introduced in version 1.8. The new widget supported icons inside the text area and reduced the screen space needed to present information, while improving GNOME integration.[20]

The next major milestone was version 2.14, which was the first to follow GNOME's version numbering. It also featured network awareness using NetworkManager, smart bookmarks improvements, and the option to build with XULRunner.

The latter was critical. Previously, Epiphany could only use an installed Mozilla web browser as a web engine provider. The XULRunner support made it possible to install Epiphany as the only web browser on the system.[21][22]


The development process suffered from major problems related to the Gecko backend.[17] To address these issues, in July 2007, the Epiphany team added support for WebKit as an alternative rendering engine.[23] On April 1, 2008, the team announced that it would remove the ability to build it using Gecko and proceed using only WebKit.[17]

The size of the team and complexity of porting the browser to Webkit caused version 2.22 to be re-released with bugfixes alongside GNOME 2.24,[24] so the releases stagnated until July 1, 2009, when it was announced that 2.26 would be the final Gecko-based version.[25]

In September 2009, the transition to Webkit was completed as part of GNOME 2.28.[26]

Release history


Web Standards Support

The underlying WebKit browser engine provides support for HTML 4, XHTML, CSS 1 and 2, most of HTML 5 and CSS 3,[69] and a Web Inspector (web development debugging tool).[52]

Web once supported NPAPI plugins, such as Java and Adobe Flash, but with the modern web platform, these plugins have fallen out of favor and are being deprecated in major browsers and, in the case of Flash, by Adobe itself.[70] Additionally, Flash had gained infamy throughout the years for usability and stability issues, incessant security vulnerabilities,[71] its proprietary nature, its ability to let sites deploy particularly obnoxious web ads,[72] and Adobe's poor and inconsistent Linux support.[73] Many of these issues were raised by Steve Jobs, then CEO of Apple, in his essay Thoughts on Flash.[74] Since GNOME Web 3.34 and WebkitGTK 2.26, plugin support is removed.[75]

GNOME Integration

Web reuses GNOME frameworks and settings,[76][77] including the user interface theme, network settings, and printing. Settings are stored with GSettings and GNOME default applications are used for internet media types handling. The user configures these, centrally, in GNOME's settings app.

The built-in preference manager for Web presents basic browser-specific settings while advanced settings which could radically alter Web's behavior can be changed with utilities such as dconf (command line) and dconf-editor (graphical).[78]

Web follows the GNOME Human Interface Guidelines and platform-wide design decisions.[79] For example, in Web 3.4, the menu for application actions was moved to the GNOME Shell's top panel application menu and the menu bar was replaced with "super menu" button, which triggers the display of window-specific menu entries.[80]

Since GNOME 3.32, Web can adjust to various form factors with the help of libhandy, a library sponsored by Purism.[81] It supports desktop, tablet and phone form factors. ("Narrow Mode") [82]

Ad Blocking and Do Not Track

Since GNOME 3.18, Web is configured to block ads and pop-ups by default, and to send Do Not Track headers to websites,[65]. Other browsers typically make the user seek out an extension and toggle settings.

In GNOME 3.34, the existing ad blocker was removed. This code was only partially functional and had been the source of many bugs. Web adopted the "Content Blockers" system from the Webkit engine.[83][84][85]

One of the developers, Adrián Pérez de Castro, compared the old and new ad blockers. He found that the switch saved approximately 80 MiB of RAM per browser tab.[86]

Google Safe Browsing and Security Sandboxing

Since GNOME 3.28, Web has support for Google Safe Browsing, to help prevent users from visiting malicious websites.[10]

Since GNOME 3.34, Web explicitly requires a minimum of WebkitGTK 2.26 or later.[87][88][89] This provides the "Bubblewrap Sandbox"[90] for tab processes, which is intended to prevent malicious websites from hijacking the browser and using it to spy on other tabs or run malicious code on the user's computer. If such code found another exploit in the operating system allowing it to become root, the result could be a disaster for all users of the system.

Making the sandbox a priority was brought on, according to Michael Catanzaro, because he was particularly concerned with the code quality of OpenJPEG and the numerous security problems that had been discovered in it, including many years of failing security reviews by Ubuntu.[91] He further explained that web compatibility requires that sites believe that Web is a major browser. Sending them the user agent of Apple Safari causes fewer broken websites than others (due to sharing the Webkit engine), but also causes caching servers to deliver JPEG 2000 images,[92] of which Safari is the only major browser to support. There is no other usable open source option for JPEG 2000 support. Fixing OpenJPEG, which is the official reference software, will be a massive undertaking that could take years to sort out. Enabling the Bubblewrap Sandbox would cause many vulnerabilities in this and other components to become "minimally useful" to potential attackers.[93]

Smart Bookmarks

While most browsers feature a hierarchical folder-based bookmark system, Web uses categorized bookmarks, where a single bookmark (such as "Web") can exist in multiple categories (such as "Web Browsers", "GNOME", and "Computer Software").[94] A special category includes bookmarks that have not yet been categorized. Another innovative concept supported by Web (though originally from Galeon)[5] is "smart bookmarks". These take a single argument specified from the address bar, or from a textbox in a toolbar.[15] Bookmarks, along with browsing history, are accessed from the address bar in find-as-you-type manner.[95]

Web Application Mode

Since GNOME 3.2, released in September 2011,[96] Web allows creating application launchers for web applications. The subsequent invocation of a launcher brings up a plain site-specific browser (single instance) of Web limited to one domain, with off-site links opening in a normal browser.[97] The launcher created this way is accessible from the desktop and is not limited to GNOME Shell. For instance it may be used with Unity, used on Ubuntu.[98] This feature facilitates the integration of the desktop and World Wide Web, which is a goal of Web's developers.[99] Similar features can be found in the Windows version of Google Chrome. For the same purpose Mozilla Foundation previously developed a standalone application Mozilla Prism, which was superseded by the project Chromeless.[100]

Web applications are managed within the browser's main instance. The applications can be deleted from the page, accessible with a special URI about:applications. This approach was supposed to be a temporary while a centralized GNOME web application management was to be implemented in GNOME 3.4, but this never happened.[28]

Firefox Sync

Since GNOME 3.26, Web has support for Firefox Sync, which allows users to sync their bookmarks, history, passwords, and open tabs with Firefox Sync, which can then be shared between any copy of Firefox or Web that the user signs into Firefox Sync with.[101]


Web once supported extensions and a package was maintained containing the official ones. This was later removed due to problems with stability and maintainability.

Some popular extensions, such as ad blocking, were moved to the core application, while native helper apps such as Evince can render PDF documents.

The project has expressed an interest in implementing support for the WebExtension add-on format used by Chrome, Firefox, and some other major browsers, if interested contributors can be found.[102]

System requirements

Despite being a component of GNOME, Web has no requirements on beyond GNOME components[7], so it can be potentially installed on any system supporting GTK and Webkit. Though the GNOME Project does not list specific system requirements, it states that GNOME 3 should run on any modern computer.[103]


In reviewing the WebKit-powered Epiphany 2.28 in September 2009, Ryan Paul of Ars Technica said "Epiphany is quite snappy in GNOME 2.28 and scores 100/100 on the Acid3 test. Using WebKit will help differentiate Epiphany from Firefox, which is shipped as the default browser by most of the major Linux distributors."[26]

In reviewing Epiphany 2.30 in July 2010, Jack Wallen described it as "efficient, but different" and noted its problem with crashes. "When I first started working with Epiphany it crashed on most sites I visited. After doing a little research (and then a little debugging) I realized the issue was with JavaScript. Epiphany (in its current release), for some strange reason, doesn't like JavaScript. The only way around this was to disable JavaScript. Yes this means a lot of features won't work on a lot of sites – but this also means those same sites will load faster and won't be so prone to having issues (like crashing my browser)."[94] Wallen concluded positively about the browser, "Although Epiphany hasn't fully replaced Chrome and Firefox as my one-stop-shop browser, I now use it much more than I would have previously.[94] [It has a] small footprint, fast startup, and clean interface."[94]

In March 2011, Veronica Henry reviewed Epiphany 2.32, saying "To be fair, this would be a hard sell as a primary desktop browser for most users. In fact, there isn't even a setting to let you designate it as your default browser. But for those instance where you need to fire up a lighting-fast browser for quick surfing, Epiphany will do the trick."[104] She further noted, "Though I still use Firefox as my primary browser, lately it seems to run at a snail's pace. So, one of the first things I noticed about Epiphany is how quickly it launches. And subsequent page loads on my system are equally as fast."[104] Henry criticized Epiphany for its short list of extensions, singling out the lack of Firebug as a deficiency.[104] Web instead supports Web Inspector offered by the WebKit engine, which has similar functionality.[52]

In April 2012, Ryan Paul of Ars Technica used Web as an example to his criticism of GNOME 3.4 design decisions: "Aside from the poor initial discoverability of the panel menu, this model works reasonably well for simple applications. [...] Unfortunately, it doesn't scale well in complex applications. The best example of where this approach can pose difficulties is in GNOME's default Web browser. [...] Having the application's functionality split across two completely separate menus does not constitute a usability improvement."[80] This was addressed in later versions, with a single unified menu.

In an October 2016 review, Bertel King Jr. noted on MakeUseOf, "Later versions offer the best integration you will find with GNOME Shell. It lacks the add-ons found in mainstream browsers, but some users will like the minimalism, the speed, and the tab isolation that prevents one misbehaving site from crashing the entire browser."[105]

In an April 2019 review, Bertel King Jr. wrote another article on MakeUseOf, this time reviewing GNOME Web for its Web Applications Mode. He stated, "When you check your email, you’re using a web app. If you open YouTube, Netflix, or Spotify in a browser, again, you’re using a web app. These days, you can replace most of your desktop apps with web apps. [...] GNOME Web provides tools to better integrate web apps with the rest of your desktop, so you can open them via your app launcher and view them in your dock or taskbar. This way they feel more like apps and less like sites." He also praised the security provided by walling off Web Applications from the rest of the browser and each other. Like Mozilla's container feature, this helps prevent sites such as Facebook from seeing what the user is doing in the main browser. It also allows the user to create multiple "apps" for the same site, to easily switch between different accounts.[9]

See also


  1. "Contributors · GNOME / Epiphany · GitLab". Retrieved March 15, 2017.
  2. "Epiphany turns 7", The GNOME Web Browser Developers, December 24, 2009, retrieved June 15, 2011
  3. Petridis, Jordan (November 25, 2019). "GNOME 3.34.2 Released". GNOME Mail Services (Mailing list). Retrieved December 14, 2019.
  4. Catanzaro, Michael (November 24, 2019). "GNOME 3.35.2 released". GNOME Mail Services (Mailing list). Retrieved November 29, 2019.
  5. DeRosia, Chris (July 29, 2003), Galeon, A History or, why Galeon is the way it is, retrieved October 16, 2011
  6. "Frequently Asked Questions". Retrieved June 13, 2019.
  7. "Arch Linux – epiphany 3.34.0–1 (x86_64)". October 1, 2019.
  8. "GNOME Web Browser is Adding a Reader Mode – OMG! Ubuntu!". June 22, 2018. Retrieved June 13, 2019.
  9. "5 Reasons to Start Using GNOME Epiphany Web Apps". April 4, 2019. Retrieved June 13, 2019.
  10. "Epiphany 3.28 Development Kicks Off With Safe Browsing, Better Flatpak Handling – Phoronix". Retrieved April 9, 2018.
  11. The GNOME Project, September 28 (March 28, 2012), "GNOME 3.4 Release Notes", gnome-announce mailing list
  12. "Epiphany README", Epiphany Git repository, retrieved May 20, 2016
  13. Canonical Ltd (April 22, 2016). "epiphany-browser package in Ubuntu". Retrieved May 20, 2016.
  14. "Overview - rpms/epiphany -". Retrieved October 1, 2019.
  15. Min, Andrew, "Epiphany, the ultimate Gnome browser", The Ubuntu Applications book (under construction), Free Software Magazine, archived from the original on October 31, 2008, retrieved October 16, 2011
  16. Marco Pesenti Gritti (December 8, 2002), Epiphany's initial home page, archived from the original on April 24, 2003, retrieved October 17, 2011
  17. Persch, Christian (April 1, 2008), "ANNOUNCEMENT: The Future of Epiphany", epiphany mailing list-list
  18. "Marco". Retrieved November 28, 2015.
  19. Granneman, Scott (2005), Don't click on the blue e!: switching to Firefox, Sebastopol, CA, United States: O'Reilly Media (published October 16, 2005), p. 201, ISBN 0-596-00939-9
  20. "New text entry field with focus indication and icons", The GNOME Web Browser Developers, August 3, 2005, retrieved October 17, 2011
  21. "π -1", The GNOME Web Browser Developers, March 14, 2006, retrieved October 16, 2011
  22. "1.9.8 released; XULRunner", The GNOME Web Browser Developers, February 27, 2006, retrieved October 17, 2011
  23. Lopez, Xan (July 24, 2007), If you see the Buddha on the road, port it to GTK, retrieved November 25, 2011
  24. Lopez, Xan (April 6, 2008), Epiphany ♥ WebKit, retrieved November 25, 2011
  25. "Gecko end-of-life", The GNOME Web Browser Developers, July 1, 2009, retrieved November 25, 2011
  26. Paul, Ryan (September 24, 2009), "Linux garden gets a new GNOME with version 2.28", Ars Technica, retrieved October 16, 2011
  27. "GNOME Release Notes", The GNOME Project, retrieved October 16, 2011
  28. "NEWS file", The GNOME Project's git repository, retrieved October 17, 2011
  29. Gritti, Marco Pesenti (December 25, 2002), "[Epiphany] Epiphany 0.4", epiphany mailing list
  30. Gritti, Marco Pesenti (April 13, 2003), "[Epiphany] Epiphany 0.5.0", epiphany mailing list
  31. Gritti, Marco Pesenti (May 4, 2003), "[Epiphany] Epiphany 0.6.0", epiphany mailing list
  32. Gritti, Marco Pesenti (June 7, 2003), "[Epiphany] Epiphany 0.7.0", epiphany mailing list
  33. "Epiphany 0.8.0 Released", mozillaZine, July 13, 2003, archived from the original on November 26, 2010, retrieved October 17, 2011
  34. Gritti, Marco Pesenti (August 22, 2003), "[Epiphany] Epiphany 0.9.0", epiphany mailing list
  35. Gritti, Marco Pesenti (September 8, 2003), "[Epiphany] Epiphany 1.0", epiphany mailing list
  36. Gritti, Marco Pesenti (March 15, 2004), "Epiphany 1.2.0", epiphany mailing list
  37. Persch, Christian (September 13, 2004), "Epiphany 1.4.0", epiphany mailing list
  38. Persch, Christian (March 9, 2005), "Epiphany 1.6.0", epiphany mailing list
  39. van Schouwen, Reinout (September 5, 2005), "Epiphany and Epiphany-extensions 1.8.0", epiphany mailing list
  40. van Schouwen, Reinout (March 12, 2006), "Epiphany 2.14.0 released!", epiphany mailing list
  41. "Topic suggestions", The GNOME Web Browser Developers, January 22, 2006, retrieved October 17, 2011
  42. Newren, Elijah (September 6, 2006), "Celebrating the release of GNOME 2.16!", gnome-announce mailing list, retrieved September 20, 2007
  43. "Epiphany 2.16 Release Notes", The GNOME Project, March 2, 2008, archived from the original on September 8, 2008, retrieved October 17, 2011
  44. "A new stabler stable release", The GNOME Web Browser Developers, January 30, 2007, retrieved October 16, 2011
  45. Newren, Elijah (March 14, 2007), "Celebrating the release of GNOME 2.18!", gnome-announce mailing list, retrieved September 20, 2007
  46. "Foresight and Epilicious", The GNOME Web Browser Developers, March 4, 2007, retrieved October 16, 2011
  47. Paul, Ryan (September 19, 2007), "GNOME 2.20 officially released", Ars Technica, retrieved September 20, 2007
  48. Untz, Vincent (March 12, 2008), "Celebrating the release of GNOME 2.22!", gnome-announce mailing list-list, retrieved March 12, 2008
  49. Untz, Vincent (September 24, 2008), "Celebrating the release of GNOME 2.24!", gnome-announce mailing list-list, retrieved September 27, 2008
  50. Untz, Vincent (March 18, 2009), "Celebrating the release of GNOME 2.26!", gnome-announce mailing list-list, retrieved March 18, 2009
  51. Holwerda, Thom (September 24, 2009). "GNOME 2.28 Released". OSNews. Retrieved April 5, 2009.
  52. Hatcher, Timothy (September 30, 2008), "Web Inspector Redesign", Webkit developers blogs, retrieved October 18, 2011
  53. Holwerda, Thom (March 31, 2010). "GNOME 2.30 Released". OSNews. Retrieved April 4, 2010.
  54. Untz, Vincent (September 29, 2010), "Celebrating the release of GNOME 2.32!", gnome-announce mailing list
  55. Untz, Vincent (April 6, 2011), "GNOME 3.0 Released", gnome-announce mailing list
  56. Clasen, Matthias (September 28, 2011), "GNOME 3.2 Released", gnome-announce mailing list
  57. The GNOME Project, September 26 (September 26, 2012), "GNOME 3.6 Release Notes", gnome-announce mailing list
  58. The GNOME Project, March 27 (March 27, 2013), "GNOME 3.8 Release Notes", gnome-announce mailing list
  59. "Epiphany source coder". Gnome. September 26, 2013. Retrieved October 14, 2013.
  60. "Epiphany source code". Gnome. March 25, 2014. Retrieved March 31, 2014.
  61. "3.12 Released with New Features for Users and Developers". GNOME. March 26, 2014. Retrieved April 7, 2014.
  62. "epiphany – A simple, clean, beautiful view of the Web". Gnome. September 24, 2014. Retrieved October 14, 2014.
  63. "Epiphany 3.14 News file". GNOME. September 24, 2014. Retrieved October 14, 2014.
  64. "epiphany – A simple, clean, beautiful view of the Web". Retrieved December 3, 2015.
  65. "epiphany – A simple, clean, beautiful view of the Web". Retrieved December 3, 2015.
  66. The GNOME Project, September 6 (September 6, 2018), "GNOME 3.30 Release Notes", gnome-announce mailing list
  69. "SpecSupport", WebKit project, retrieved November 14, 2011
  72. "Adobe U-Turns, Decides to Support Flash for Linux".
  73. "Chrome will block obnoxious Flash ads starting September 1st".
  74. "Thoughts on Flash – Apple".
  76. Grand, Rickford (2004), Linux for non-geeks: a hands-on, project-based, take-it-slow guidebook, San Francisco, United States: No Starch Press (published October 16, 2004), pp. 116–117, ISBN 1-59327-034-8
  77. Peterson, Richard (May 2009), Fedora 10 Linux Desktop, San Francisco, United States: Surfing Turtle Press (published June 15, 2008), p. 224, ISBN 0984103627
  78. Dalheimer, Matthias Kalle; Welsh, Matt (December 22, 2005), Running Linux (March 28, 5 ed.), Sebastopol, CA, United States: O'Reilly Media (published March 28, 2006), p. 94, ISBN 978-0-596-00760-7
  79. McCallister, Michael (January 2006), SUSE Linux 10 unleashed, Unleashed Series, United States: Sams Publishing (published October 16, 2006), p. 225, ISBN 0-672-32726-0
  80. Paul, Ryan (April 1, 2012), "Hands-on: GNOME 3.4 arrives, introducing significant design changes", Ars Technica, retrieved April 1, 2012
  94. Wallen, Jack (July 2010). "Epiphany: An efficient, but different, web browser". Retrieved March 24, 2011.
  95. "Smart Bookmarks", The GNOME Project, retrieved December 14, 2011
  96. Vitters, Olav; Klapper, André; Day, Allan (September 28, 2011), "GNOME 3.2 Release Notes", The GNOME Project, retrieved October 16, 2011
  97. Lopez, Xan (August 31, 2011), Web application mode in GNOME 3.2, retrieved October 16, 2011
  98. Andrew (October 3, 2011), Install Epiphany 3.2.0 with Web Application mode in Ubuntu 11.10 Oneiric Ocelot, retrieved October 16, 2011
  99. Lopez, Xan (April 11, 2011), The Web comes to GNOME, ready or not, retrieved October 16, 2011
  100. Hilaiel, Lloyd (February 11, 2011), "Prism is now Chromeless", Mozilla Labs, archived from the original on August 8, 2011, retrieved November 14, 2011
  101. "On Firefox Sync – Michael Catanzaro". Retrieved September 25, 2017.
  103. "GNOME 3 Myths My computer and/or graphics card isn't powerful enough to run GNOME 3", GNOME Wiki, retrieved January 12, 2019
  104. Henry, Veronica (March 9, 2011), "Top 3 Alternative Linux Browsers", Train Signal Training, retrieved March 25, 2011
  105. King Jr, Bertel. "The Best Linux Software". Retrieved October 11, 2016.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.