We cover some of the most innovative features to land in Firefox 52, including WebAssembly, CSS Grid, the CSS Grid Inspector Tool, an improved Responsive Design Mode, and Async and Await support for JavaScript.
Unlike JavaScript, WebAssembly is a binary format, which means developers need new tools to help understand and experiment with WebAssembly. Discover the basic functions of the WebAssembly Explorer, which lets developers type in simple C or C++ programs and compile them to WebAssembly.
The Containers feature in Firefox Nightly gives users the ability to place barriers on the flow of data across sites by isolating cookies, indexedDB, localStorage, and caches within discrete browsing contexts. After running the Containers UI through successive rounds of user research and UX iteration, we’ve launched a Containers experiment in Firefox Test Pilot in order to widen the audience for Containers, iterate on the UI, and reason about the future of the feature.
In July of 2015 we announced our Games Technology Roadmap, and we've been working steadily on addressing those pain points as shared by developers. Here's an overview of the newest platform developments and the progress we've made.
Mozilla has partnered with BrowserStack to offer free testing on mobile Firefox for Android (iOS upcoming). Not every developer owns a device bank or has the time to test on every OS. Mozilla is committed to ensuring a healthy and robust web. Cross-browser compatibility is a key component of that commitment.
WebAssembly is a way of taking code written in programming languages other than JavaScript and running that code in the browser. So when people say that WebAssembly is fast, what they are comparing it to is JavaScript. In this series, I want to explain to you why WebAssembly is fast.
This is the second part in a series on WebAssembly and what makes it fast. If you haven’t read the others, we recommend starting from the beginning. JavaScript started out slow, but then got faster thanks to something called the JIT. This article is about how the JIT works.
To understand how WebAssembly works, it helps to understand what assembly is and how compilers produce it. Third part in a series on WebAssembly and what makes it fast. We recommend starting from the beginning.
WebAssembly is a way to run programming languages other than JavaScript on web pages. In the past when you wanted to run code in the browser to interact with the different parts of the web page, your only option was JavaScript. So when people talk about WebAssembly being fast, the apples to apples comparison is to JavaScript. Fourth in a series on WebAssembly.
Programming with WebAssembly or JavaScript is not an either/or choice. So developers don’t need to choose between WebAssembly and JavaScript. However, we do expect that developers will swap out parts of their JavaScript code for WebAssembly. Fifth in a series about WebAssembly.
On February 28, the four major browsers announced their consensus that the MVP of WebAssembly is complete. Even in the initial release, WebAssembly will be fast. But it should get even faster in the future, through a combination of fixes and new features. Sixth in a series about WebAssembly.
