This blog post examines how one can dynamically evaluate code in JavaScript.

This blog post describes five technologies that will make 2014 an exciting year for the web platform:

1. asm.js: near-native performance on the web
2. ParallelJS: parallelized JavaScript code
3. ECMAScript 6 (ES6): evolving the language, uniting the community
4. Web Components: a standard infrastructure for widgets
5. CSS Grid Layout: native-like GUI layout

GitHub displays Markdown files so nicely, it’s a shame there is no print view where all the toolbars etc. are hidden. Note that printing doesn’t necessarily mean that paper is involved. For example, on Mac OS X, you can print to PDF files.

This blog post explains three ways of printing Markdown files that are hosted on GitHub:

Update 2017-05-08: a proposal for SIMD.js has been rejected, in favor of providing similar functionality via WebAssembly.

Recently, a new JavaScript feature has landed for the next Firefox Nightly: an API for SIMD (Single Instruction, Multiple Data). This blog post explains how the API works and how it fits into the JavaScript landscape.

Update 2014-05-08. Newer version of this post: “ECMAScript 6’s new array methods”

Two new Array methods (proposed by Rick Waldron) are in the latest ECMAScript 6 specification draft:

• Array.prototype.find()
• Array.prototype.findIndex()

This blog post describes them.

Updates:

• [2015-01-05] ParallelJS has failed. It apparently wasn’t powerful enough. Its experimental implementation will be removed from SpiderMonkey (Firefox’s JavaScript engine).
• [2013-12-28] A low-level JavaScript API for SIMD is another avenue for parallelization (within a single processer core).

JavaScript is still a very sequential language. That is slowly changing. This blog post describes ParallelJS, an effort to bring data parallelism to JavaScript.

If you want to use strict mode [1] in the Node.js REPL, you have two options.

Tweet by Leon Arnott:

#TIL the reason the DOM has so many "array-like objects" that aren't functional arrays… is because in Javascript 1.0, there were no arrays.

It is not a frequent use case, but it comes up occasionally: Producing an array [1] of a given length that is filled with values. This blog post explains how to do it and what to watch out for.

Update 2013-11-22: David Herman has published the slide deck “Status Report: ES6 Modules”.

[1] is an introduction to ECMAScript 6 modules and how they can be used in current browsers. In contrast, this blog post explains how future browsers will support them natively. As part of that support, we will get the <module> tag, a better version of the <script> tag.