Connect with us


If you’re looking to speed up Firefox page renders, Jack Wallen shows you how to enable the new composite engine, WebRender.

Image: Mozilla

WebRender has been in the works for some time now. Built as a GPU-based 2D rendering engine written in Rust, the purpose of WebRender is to make the rendering of pages both faster and smoother. Although that feature has been in the planning for a while, it has yet to be rolled out full scale.

If you’re using version 67 or newer of Firefox (which you should be, as that’s a fairly old version of the browser), you can enable this rendering engine. Surprisingly enough, even using version 78.0.2 on Linux, macOS, and Windows or the Nightly version on Linux shows that WebRender is not enabled by default.

Once I enabled the feature, I did see noticeably faster page renders. So even though WebRender isn’t quite ready for mass adoption, it is already showing serious promise and stability.

So how do you enable this feature to enjoy faster and smoother page renders? Let me show you.

SEE: Hiring kit: Network administrator (TechRepublic Premium)

What you’ll need

In order to enable WebRender you’ll need a recent release of the Firefox web browser on any desktop or laptop platform. 

How to enable WebRender

Open your Firefox web browser. In the address bar type:

about:config

You’ll be warned that there are risks looming ahead (Figure A).

Figure A

webrender-warning.jpg

You’ve been thoroughly warned of the risks.

Click Accept The Risk And Continue. In the resulting window, type the following in the search bar (Figure B):

gfx.webrender.all

Figure B

webrender-search.jpg

The about:config main window.

You should immediately see the gfx.webrender.all entry appear (Figure C).

Figure C

webrenderd.jpg

The gfx.webrender.all entry in about:config.

Click the right- and left-pointing arrows to the far right of the entry to toggle gfx.webrender.all from false to true. Once you see true in the center, close and restart Firefox. When Firefox reopens, type the following in the address bar:

about:support

Hit Enter on your keyboard and, when the page loads, scroll down to the Graphics section. You should see Compositing listed as WebRender (Figure D).

Figure D

webrenderf.jpg

We’ve successfully switched from the basic compositing engine to WebRender.

I was able to enable WebRender for both Linux and macOS versions of Firefox. On Windows 10, however, I was not. Even though about:config showed WebRender was enabled, about:support still listed the Compositing engine as basic. This could simply be because my Windows 10 instance was running as a VirtualBox VM. Interestingly enough, however, an instance of Ubuntu Linux running as a VirtualBox VM did accept the changes, so your mileage may vary.

And that’s all there is to enabling the Mozilla WebRender compositing engine on Firefox. Make this so and see if your page render times are able to reach warp speed. 

Also see



Source link

0
Continue Reading

Technology

Open source: Why governments need to go further

dc

Commentary: Yes, governments should open source their custom code. But more than that is needed.

Image: lucky-photographer, Getty Images/iStockphoto

For Drupal (and Acquia) founder Dries Buytaert, “the default [in government] should be ‘developed with public money, make it public code.'” That is, if a government is paying for software to be created, that software should be available under an open source license. While he acknowledged there might be exceptions (e.g., for military applications, as I’ve called out), his suggestion makes sense.

Years ago I argued that government mandates of open source made no sense. I still feel that way. Governments (and enterprises) should use whatever software best enables them to get work done. Increasingly, that software will be open source. But when good open source alternatives don’t yet exist, it makes no sense to mandate the use of suboptimal software. 

But software that governments create? There’s no compelling citizen-focused reason for closing it off. Instead, there are many reasons to open it up.

SEE: How to build a successful developer career (free PDF) (TechRepublic)

Of the people, by the people, for the people

This topic of why countries should embrace open source is an easy argument to make. As Buytaert pointed out, if public money pays for the code to be developed, why wouldn’t that code be available to the public (except, as mentioned, in the case of sensitive military software)? 

Some countries have already gone this route. As I detailed in 2016, Bulgaria is one of them. A few years later, Bulgaria has been preparing its own national source code repository, based on Git (as required by law: “administrative authorities shall use public storage and control systems for the source code and technical documentation for development, upgrading or deployment of information systems or electronic services”). 

This is a significant step toward greater transparency. However, it’s not enough.

SEE: Open source can thrive in a recession says Drupal creator Dries Buytaert (TechRepublic)

Collaborating on common government issues

As much as I understand Bulgaria’s desire to build its own source code repository, there’s even greater need for governments to collaborate on code beyond their borders. Think about it: Governments tend to do the same things, like collecting taxes, issuing parking tickets, etc. Currently, each government builds (or buys) software to tackle these tasks. Obscene quantities of custom code are created each year by government organizations operating in silos.

Why isn’t the city of Bogota sharing software with London, which shares software with Lagos, which shares software with Pocatello (that’s in Idaho, by the way)? 

As IBM president (and former Red Hat CEO) Jim Whitehurst said way back in 2009, “The waste in IT software development is extraordinary….Ultimately, for open source to provide value to all of our customers worldwide, we need to get our customers not only as users of open source products but truly engaged in open source and taking part in the development community.” This is particularly true in government, where there isn’t even the competitive pressure (e.g., Bogota doesn’t compete with Pocatello) that might prevent large financial institutions from collaborating (though even they partner on open source).

So, yes, we need governments to open source the software they pay to have built, to Buytaert’s point. But we also need those same governments to share that code beyond their borders, thereby driving greater innovation at lower cost for their citizens. 

Disclosure: I work for AWS but the views expressed herein are mine, not those of my employer.

Also see

Source link

0
Continue Reading

Technology

Elastica: A Compliant Mechanics Environment for Soft Robotic Control

artificial intelligence 3382507 960 720

Soft robots can be used in various spheres, such as agriculture, medicine, and defense. However, their complex physics means that they are hard to control. Current simulation testbeds are insufficient for taking the full advantage of elasticity.

A recent paper on arXiv.org proposes Elastica, a simulation environment tailored to soft robot context. It tries to fill the gap between conventional rigid body solvers, which are incapable to model complex continuum mechanics, and high-fidelity finite elements methods, which are mathematically cumbersome. Elastica can be used to simulate assemblies of soft, slender, and compliant rods and interface with major reinforcement learning packages. It is shown how most reinforcement learning models can learn to control a soft arm and to complete successively challenging tasks, like 3D tracking of a target, or maneuvering between structured and unstructured obstacles.

Soft robots are notoriously hard to control. This is partly due to the scarcity of models able to capture their complex continuum mechanics, resulting in a lack of control methodologies that take full advantage of body compliance. Currently available simulation methods are either too computational demanding or overly simplistic in their physical assumptions, leading to a paucity of available simulation resources for developing such control schemes. To address this, we introduce Elastica, a free, open-source simulation environment for soft, slender rods that can bend, twist, shear and stretch. We demonstrate how Elastica can be coupled with five state-of-the-art reinforcement learning algorithms to successfully control a soft, compliant robotic arm and complete increasingly challenging tasks.

Link: https://arxiv.org/abs/2009.08422