4 min read

Yesterday Facebook released a new JavaScript engine called Hermes under an open source MIT license. According to Facebook, this new engine will speed up start times for native Android apps built with React Native framework.

Today Facebook is open sourcing Hermes, a small and lightweight JavaScript engine optimized for running React Native on Android. We are currently publishing a new patch release for React Native which will contain Hermes as opt-in. https://t.co/YUFCqvTrAV — React Native (@reactnative) July 11, 2019

Facebook software engineer Marc Horowitz unveiled Hermes at the Chain React 2019 conference held yesterday in Portland, Oregon. Hermes is a new tool for developers to primarily improve app startup performance in the same way Facebook does for its apps, and to make apps more efficient on low-end smartphones.

The supposed advantage of Hermes is that developers can target all three mobile platforms with a single code base; but as with any cross-platform framework, there are trade offs in terms of performance, security and flexibility. Hermes is available on GitHub for all developers to use. It has also got its own Twitter account and home page.

In a demo, Horowitz showed that a React Native app with Hermes was fully loaded within half the time the same app without Hermes loaded, or about two seconds faster. Check out the video below:

Horowitz emphasized on the fact that Hermes cuts the APK size (the size of the app file) to half the 41MB of a stock React Native app, and removes a quarter of the app’s memory usage.

In other words, with Hermes developers can get users interacting with an app faster with fewer obstacles like slow download times and constraints caused by multiple apps sharing in a limited memory resources, especially on lower-end phones.

And these are exactly the phones Facebook is aiming at with Hermes, compared to the fancy high-end phones that well-paid developers typically use themselves.

“As developers we tend to carry the latest flagship devices. Most users around the world don’t,” he said. “Commonly used Android devices have less memory and less storage than the newest phones and much less than a desktop. This is especially true outside of the United States. Mobile flash is also relatively slow, leading to high I/O latency.”

It’s not every day a new JavaScript engine is born, but while there are plenty such engines available for browsers, like Google’s V8, Mozilla’s SpiderMonkey, Microsoft’s Chakra, Horowitz notes Hermes is not aimed at browsers or, for example, how Node.js on the server side.

“We’re not trying to compete in the browser space or the server space. Hermes could in theory be for those kinds of use cases, that’s never been our goal.”

The Register reports that Facebook has no plan to push Hermes’ beyond React Native to Node.js or to turn it into the foundation of a Facebook-branded browser. This is because it’s optimized for mobile apps and wouldn’t offer advantages over other engines in other usage scenarios.

Hermes tries to be efficient through bytecode precompilation – rather than loading JavaScript and then parsing it. Hermes employs ahead-of-time (AOT) compilation during the mobile app build process to allow for more extensive bytecode optimization. Along similar lines, the Fuchsia Dart compiler for iOS is an AOT compiler.

There are other ways to squeeze more performance out of JavaScript. The V8 engine, for example, offers a capability called custom snapshots. However, this is a bit more technically demanding than using Hermes.

Hermes also abandons the just in time (JIT) compiler used by other JavaScript engines to compile frequently interpreted code into machine code. In the context of React Native, the JIT doesn’t do that much to ease mobile app workloads.

The reason Hermes exists, as per Facebook, is to make React Native better. “Hermes allows for more optimization on mobile since developers control the build stack,” said a Facebook spokesperson in an email to The Register. “For example, we implemented bytecode precompilation to improve performance and developed more efficient garbage collection to reduce memory usage.”

In a discussion on Hacker News, Microsoft developer Andrew Coates claims that internal testing of Hermes and React Native in conjunction with Microsoft Office for Android shows TTI using Hermes at 1.1s, compared to 1.4s for V8, and with 21.5MB runtime memory impact, compared to 30MB with V8.

Hermes is mostly compatible with ES6 JavaScript. To keep the engine small, support for some language features is missing, like with statements and local mode eval().

Facebook’s spokesperson also said to The Register that they are planning to publish benchmark figures in the next week to support its performance claims.

Read Next

Declarative UI programming faceoff: Apple’s SwiftUI vs Google’s Flutter

OpenID Foundation questions Apple’s Sign In feature, says it has security and privacy risks

Material-UI v4 releases with CSS specificity, Classes boilerplate, migration to Typescript and more