Why has a great impact on our
Microsoft is rebuilding Edge from the ground up using the chromium code that also underpins Google Chrome. Most importantly, it is a switch to a different browser rendering engine. The question is, what exactly is such a rendering engine? And how can it make any change in our browsing experience? Obviously, that seems to be what Microsoft wants us to know in this post.
When accessing the internet, the web browser you choose means you choose the and a . Sometimes, the two terms are used separately and sometimes to mean the same thing. Practically, the renders the pages and the handles the communications between the and the browser user interface.
However, in terms of rendering , there three main to consider: Webkit (powering browser), Gecko (powering Mozilla browser), and Blink (powering , Opera, Brave, & many others).
Though the report source is not covering it in details, Chromium should not get you confused. It is just like a step between Blink and the full Google (or the new edge), it is a barebone, open source browser, which others can build on top of.
Since you have known the names of the three major browser , so what exactly are they? What is their function? The answer is very simple. Their job is to take the CSS, HTML and other code of a webpage like the text you can see in the page source or open in a text editor, setting out layouts, page content, and styling and convert it into what you actually see on screen.
Ideally, the engine is like a translator, turning the raw code that you cannot understand into a comprehensive layout page of text and graphics that you can read. The browser engine makes choices about how to interpret what a web developer has typed, how particular lines of code affect what is on screen.
In fact, you can consider the to be the most important part of the browser, just like a is the most important unit of any . Everything else like the menus, extensions, smart rendering, and autofill are beautiful redundant if someone cannot see the sites he/she is visiting properly.
Since the browser are working perfectly, why do we need different ones? The answer is simple, to meet up the demand of different programmers. Different programmers have different ideas about how best to do the job of a browser engine- displaying colors, optimizing codes, refreshing pages, and many others.
Assuming you want to introduce a new and improved way for web developers to show videos embedded inside text on a webpage, you will need support from a , if you do not get it and a lot of other engineers agree with you, you might consider creating your own , which usually how browsing got where it is today. However, there is no huge change of a new ever getting off the ground in the future as predicted by .
The main reason that webpages sometimes appear, load and differently in different browsers is the browser . It is more likely the variations between Gecko, Webkit, and Blink than the variations between , , and that are behind the differences.
Meanwhile, as the internet world grows, the variations are becoming small on the surface visuals (which are pretty much the same across the board) and more about the underlying technologies.
HOW THE BROWSER DIFFER
Every part of a page’s rendering and the way user interactions are handled is carried out by the , and while each of the do a lot of processing in the same way, there are some differences too. Take the way the security of web apps is handled, this is something that each can approach differently.
‘Quantum’ is a current upgrade to Gecko, according to the engineers, they are currently on the project. It focuses on a lot of these new considerations for modern websites. It includes; how web apps get refreshed, how the browser handles memory and CPU core time, and how it responds to system crashes.
The questions of whether a will support older web standard and potentially lose milliseconds checking them- which is why built Edge1.0 in the first place, Whether it should render text first and then load images, and How it should handle multiple processes in multiple tabs. Are what will differentiate the browser of today and in the future.
For instance, what will differentiate modern browser are these high-level questions and the fewer intricacies of web fonts and embedded audio, etc. they can handle easily. Based on the existing web standards, browser also need to support new standards as the internet gets ever-more complex. This is another area where blink possibly has an advantage. With Google so many cutting-edge web apps, it is in a better position to push for the standards they use.
Other issues also exist especially the ones that only matter to developers, such include: how faster a code can be added and approved, the procedures for fixing bugs, how closely the is tied to the actual browser since the end users would not notice these unless they are counting the frequency of update patches, but they are important to mention as well.
When considering whether to stick with your current browser engine or to switch to another, you need to know that on the level, there is no huge difference between them at the moment. Chrome using Blink, Firefox uses Gecko, and Safari using Webkit, all deliver most websites in very similar ways at very similar speeds. The reason is that they all largely accept similar basic web standards- something which is not always the case. There is no headline feature we can point out that would necessarily make you suddenly leave Webkit and switch to Gecko or vice versa.
On a particular level, blink seems to be the best. It is speedy at rendering pages and apps, updates are pushed out rapidly, it is relatively robust, and bugs tend to be patched quickly. Perhaps that could be the reason switched to it, after all.
Based on Microsoft’s viewpoint, Blink appears to be the easiest to build a new browser on top of and it works best when embedded in desktop apps. At the same time, it continues to hog memory on some occasions and has grown more bloated over the years.
With the Quantum upgrade for Gecko, serious speed improvements are being handled by the Firebox engineers in a continuous effort to impress its users.
Meanwhile, Apple’s Webkit seems to have its detractors, while is still getting better on macOS and iOS –mainly due to features built on top of the and more.
Based on the statistics, the differences in these browser have no significant impact on the end users, so there would not be any need to switch your browser based on it. In other words, you can carry on by using the browser you prefer.
Originally posted 2019-04-15 11:35:52.
A mechanical engineer and an NDT inspector by profession. However, I love blogging and sharing of knowledge for human intellectual development, especially relating to engineering fields, environment, and science trending updates. “Engineeringall.com” is a platform for any individual with similar passion, to do so; use the “PUBLISH YOUR ARTICLE” page at the MENU to share your personal ideas, researched knowledge, or discovered incidents, etc.to those in the engineering & & the general online communities across the globe. If you love this post please share using the social buttons below.