Google Releases Chrome 81 With Less Resource Consumption – Research Snipers

Google Releases Chrome 81 With Less Resource Consumption

Chrome 81 is ready and is available for free download for all platforms. Google brings the new version of its browser with a lot of delays because of Corona and also with the novelties one had to row back. Chrome users should strike simply because of security updates.

Google does not want to rest on its high market share with Chrome and deliver a new browser version with interesting features every six weeks; but Corona is currently also in the gearbox for Chrome Sand, so that the new stable version Chrome 81 comes with a considerable delay. But now Chrome 81 is available for Windows, Linux, macOS and a bit delayed for Android. The new version was supposed to be an all-round new product, but Google had to row back at least partially. Officially, Google closes a whopping 32 security holes with the release of Chrome 81.

Chrome users should get the update on their system via the built-in automatic of the browser in the next few days. The browser then displays an update notice and then a Chrome restart is required. If that doesn’t work or if you can’t wait any longer, do your nails right away and get the new Chrome 81 with our downloads immediately on all your devices.

Google had announced that it would reduce Chrome’s resource consumption in 2020 and so far it has kept its word. After the last release dealt with the RAM and CPU consumption of background tabs, Chrome 81 takes care of another detail. The new browser version can determine if part of the browser window is covered by another window. In this area, which is not visible to the user, Chrome does not render the content until it becomes visible again.

Tab Groups

In the last Chrome release, Google donated tab groups for some of the users. In Chrome 81, this function is distributed to more users, who can then group individual tabs into groups. By right-clicking on a tab, users can then add websites to tab groups that are color-coded and can have a common name. If you don’t see a new function yet, you can turn it on using the # tab-groups flag.

Chrome has supported encrypted DNS requests for a long time. If a DNS server from a provider is used that also offers DNS-over-HTTPS, Chrome 81 automatically switches to the encrypted DNS variant. This is the case with Cloudflare, for example.

Similar to Firefox, Chrome 81 wanted to be more resistant to insecure encryption. For TLS 1.0 and TLS 1.1, clear warnings in the browser with instructions that fill the entire browser window were planned. Chrome blocked the old encryption standards, but you could still use them via the “Advanced” item in the warning. You notice, “wanted”, “were” and “planned”, because of Corona the TLS 1.0 and TLS 1.1 have been given a new grace period, Chrome 81 has turned off the warnings in the final version.

Browser NFC

Near Field Communications (NFC) may already be familiar to some users who pay, for example, via GooglePay. Chrome 81 is now making initial attempts with Web NFC, a standard in which websites can read and write NFC tags with the appropriate support of the browser. In the future, you no longer have to build your own apps, just a website that users can then access in Chrome.

Augmented Reality (AR)

In addition to NFC, augmented reality (AR) is also a major topic for Google, which is shown by support in Chrome 81. The WebXR interface, which was introduced earlier, is expanded to include AR features. This allows virtual objects to be shown in the real world via the camera.

Leave a Reply

Your email address will not be published. Required fields are marked *