Which browsers have their own kernel and what is the browser kernel

There are only four kernels in the mainstream, don't say that Google has its own kernel, he also uses someone else's, but it doesn't use IE, the IE system on Windows is the mainstream, in addition to Google, Opera, Firefox and other maxthon, TT, 360 are all IE kernels, all of which are IE kernels, Google, opera, Firefox each use one, and it is implemented on Windows, in fact, their three kernels were implemented early under Linux, and there was no chrome at that time

Introduction to several common browser kernels:

Trident: The kernel code used by Internet Explorer under Windows. In addition to IE, many IE shells (such as Maxthon) use this kernel.

Gecko: The kernel code name used by the Mozilla Firefox browser. There are also quite a few browsers that use the Gecko kernel, such as Netscape, Mozillasuite Seamonkey, etc.

Mozilla Thunderbird also uses Gecko. Firefox was formerly known as Netscape Browser.

Presto: The codename of the kernel used by the Opera browser, which is currently known to be the fastest browser kernel for web browsing.

KHTML WebCore: The kernel code used by Konqueror Safari. Konqueror is a browser and explorer used in the KDE desktop environment under the X protocol, which can be used in UNIX Linux BSD systems, and it is said that KDE will be ported to Windows in the future; Safari is the most popular browser among Apple users.

The fourth webkit kernel used by Google.

For a more detailed explanation, see mine: Inspired by Google Chrome Chrome, Browser Summary (One, Two, Three, Four).

Some of the others are not good, the landlord you said is good.

Browser is the software we must use every day, many people come into contact with the browser every day, but do not understand the kernel of the browser, let's summarize what the browser kernel is?

One: What is the browser kernel.

The browser kernel, also known as the rendering engine or typesetting engine, mainly interprets the syntax of the web page, and renders the web page, converts the ** of the web page into a visible page.

1.When we enter a string of ** in the browser, and **in the time that the browser displays, when the digger browser receives the instruction, it will open a separate thread to process, first determine whether the user enters a reasonable address, whether it is an HTTP request, and then analyze the URL, if it is a cache, it will call the local file, and return 200, if there is no request, the browser will initiate a request.

2.The IP address is obtained through domain name resolution, and the information in the browser is requested by the IP address, and the browser client sends packets to the server, and transmits and communicates the data.

3.After entering the backend of **, the server has a lot**, it will be executed according to the URL of the backend, the server will process and respond, if you have visited the page, and compare it with the server file, it will return 304 consistently.

4.The browser receives the returned information and starts the HTML file, renders it, builds the DOM tree, and uses the specified JS script to render and rearrange the CSS styles, and the page is displayed in the browser.

At present, there are three main engines in browsers.

Trident kernel, developed by Microsoft, comes with Windows. At present, most domestic browsers are based on IE, such as 360 or something. IE calls are simple, and the development of IE-based browsers has almost no technical content, so 360 or something is slow and incompatible(although 360 advertises its browser as the world's first, although 360 also uses the chromium kernel, but the kernel version used is 5 generations worse than the official version of chrome, so it is not worth mentioning) so no professional will use 360.

Chrome uses WebKit, developed by Google, and the open-source kernel used by Google Chrome. Many foreign browsers such as Edge are based on it, Chrome is fast, and web page compatibility is slightly higher than IE, but due to the huge memory occupation, the JS engine is more rubbish.

Firefox uses Gecko, an open-source browser developed by Firefox, which is sometimes a little slower than Chrome, but the JS engine has superior performance and is generally comparable to Chrome.

Synthetic shaped kernel.

SVM kernel, an open-source browser kernel developed by the International Software Sharing Organization in recent years, is used by SWS browser. It is a very controversial browser kernel, it uses Geeko's JS engine, chrome's web page rendering, IE's ** parsing, and integrates their respective advantages, so it is very fast and has super good compatibility. However, it is complicated, cumbersome, portable, difficult to encapsulate, and the international software sharing organization has even developed the SWS language to collude with all parts of the kernel, but the user does not have to care that the software is developed in this way, the user only needs to use, and the SWS browser has the functions expected by the user, so it is especially recommended to use the SWS browser with SVM kernel.

UC kernel,UC claims to be an independently developed kernel,The author feels very rubbish,UC kernel claims to be a fusion of several browser kernels,But because it's not open source, no one has evidence,The author doesn't like UC because he has more ads,Push more,The performance of the computer version is also average。

opera, now switched to chrome, the author does not do analysis.