Slashdot Mirror
Chrome 61 Arrives With JavaScript Modules, WebUSB Support (venturebeat.com)
The latest version of Google Chrome has launched, bringing a host of new developer features like JavaScript modules and WebUSB support. An anonymous Slashdot reader shares a report from VentureBeat: Google has launched Chrome 61 for Windows, Mac, and Linux. Additions in this release include JavaScript modules and WebUSB support, among other developer features. You can update to the latest version now using the browser's built-in silent updater or download it directly from google.com/chrome. Google also released Chrome 61 for Android today. In addition to performance and stability fixes, you can expect two new features: Translate pages with a more compact toolbar and pick images with an improved image picker.
Chrome now supports JavaScript modules natively via the new element, letting developers declare a script's dependencies. Modules are already popular in third-party build tools, which use them to bundle only the required scripts. Native support means the browser can fetch granular dependencies in parallel, taking advantage of caching, avoiding duplications across the page, and ensuring the script executes in the correct order, all without a build step. Google recommends these two blog posts for more information: ECMAScript modules in browsers and ES6 Modules in Depth. Speaking of JavaScript, Chrome 61 also upgrades the browser's V8 JavaScript engine to version 6.1. Developers can expect performance improvements and a binary size reduction. The WebUSB API meanwhile allows web apps to access user-permitted USB devices. This enables all the functionality provided by hardware peripherals such as keyboards, mice, printers, and gamepads, while still preserving the security guarantees of the web.
Chrome now supports JavaScript modules natively via the new element, letting developers declare a script's dependencies. Modules are already popular in third-party build tools, which use them to bundle only the required scripts. Native support means the browser can fetch granular dependencies in parallel, taking advantage of caching, avoiding duplications across the page, and ensuring the script executes in the correct order, all without a build step. Google recommends these two blog posts for more information: ECMAScript modules in browsers and ES6 Modules in Depth. Speaking of JavaScript, Chrome 61 also upgrades the browser's V8 JavaScript engine to version 6.1. Developers can expect performance improvements and a binary size reduction. The WebUSB API meanwhile allows web apps to access user-permitted USB devices. This enables all the functionality provided by hardware peripherals such as keyboards, mice, printers, and gamepads, while still preserving the security guarantees of the web.
This just goes to show how Chrome is really driving the web forward.
While Chrome is implementing new technologies, we see Firefox basically just copying Chrome. Firefox only just got multi-process support, many years after Chrome offered it. Firefox is now moving to an extension model that's nearly identical to Chrome's. And we can't forget how Firefox's UI imitates Chrome's in so many ways.
Really, I can't think of the last innovative thing that Firefox has added. It's like they're constantly playing catch-up to Chrome now.
Even worse is Mozilla's Servo project. For those who don't know, it's Mozilla's attempt at a new browser engine, written in Rust (which itself has been quite a debacle, I think). It has had enough trouble even getting to where browsers were 15 years ago. Now each release of Chrome leaves Servo further and further behind.
With Mozilla bungling things so badly, and with Firefox's market share dropping into the low single digit percentages, it's like Google has become the only browser vendor deciding the future of the web. Sure, Apple, Microsoft and others probably have some input, but a web technology doesn't really exist until Google implements it.
HOLY FUCK! I don't want my browser to be able to give web sites access to that info!
Then click No when the browser asks you if a particular origin should be able to use a particular API. Depending on localization decisions made before launch, the No button may be labeled Deny or Block or Don't Allow.
issue 1) this was already available as of Chrome 60 (behind a flag)
issue 2) as of Chrome 62 (Canary), the modules were not (as yet) loading in the correct order.
The module loader still gets confused if the nesting is too deep (I have to manually order part of the loading).
issue 3) it's not a "new element". It is new attributes on the same old element.
Seriously, don't go with what VentureBeat says about anything technical. As if they would even have a clue.