InfoQ Homepage JavaScript Content on InfoQ
-
YouTube Switches to HTML5 Video Player
After many years of working on HTML5 support, YouTube has decided to use their HTML5 video player as the default for modern browsers, using the old Flash-based player only for legacy browsers. Using MPEG-DASH and W3C Media Source Extensions, YouTube can use Adaptive Bitrate streaming to reduce buffering and improve initial playback speed.
-
Leveraging Nashorn at Netflix
Netflix recently hosted the Silicon Valley Java User Group to talk about Nashorn, "The Hidden Weapon of JDK 8." In this presentation the Netflix Partner Tools team described how they’ve started leveraging JavaScript in their services.
-
TypeScript 1.4 Released, Adds Union Types, More ES6 Features
Microsoft delivered TypeScript 1.4, the latest version of their JavaScript language superset. The new version adds union types and template strings. Also new is a ECMAScript 6 target mode.
-
1.0.x Release for io.js
The io.js team has released version 1.0 -- but the versioning does not suggest the platform is "production ready." Despite overtaking Node, io.js clarifies the release in its own FAQ: "The choice to release as 1.0.x was not to signify that io.js should be considered production-ready, but because it was a significant enough release from Node.js to warrant a major version increment," it says.
-
Atom API 1.0 is Stable
The Atom’s team has announced a pre-release but stable version of the editor’s API.
-
6to5 JavaScript Transpiler Gains Momentum
The 6to5 JavaScript transpiler has made significant gains in its short 6 month lifespan, besting Google's Traceur transpiler in ECMAScript 6 compatibility. Developers can write ES6 code now and let 6to5 output valid ES5 for use in today's browsers. Recently 6to5 incorporated the team behind competitor esnext into the project.
-
Major release for L20n, Mozilla's Localisation Framework
Mozilla has released version 1.0 of L20n, an open source, localisation-specific scripting language.
-
What's Exciting in New JavaScript Libraries
A number of new JavaScript libraries have popped up at GitHub and we decided to take a look at some of the more promising ones.
-
2014 JavaScript in Review
2014 has been an impressive year for JavaScript and its place on the web. We've covered a lot of stories on InfoQ from MVC frameworks to small, specialized libraries.
-
Ember Update Brings Handelbars 2.0, and HTMLBars, a New Templating Library
Ember.js has released version 1.9, bringing with it support for Handlebars 2.0, as well as performance improvements, and the introduction of HTMLBars into the Ember 1.10 beta.
-
Dart 1.8: An Interview with Seth Ladd of Google
Google has released version 1.8 of Dart, bringing with it experimental support for enums. InfoQ sat down with developer advocate Seth Ladd to get more information about the feature, and the latest info on the Dart project.
-
JavaScript on a Toaster: Embedded JavaScript with Duktape
Duktape takes JavaScript beyond the confines of the browser or server with a full ECMAScript 5 compliant engine that can be embedded into any C/C++ project.
-
Io.js, Node.js Fork, Plans First Release for January 2015
Io.js officially launched this week. A GitHub fork of joyent/node where contributions, releases, and contributorship are under an open governance model, plans its first release for January 2015. With some core members of the Node.js community dissatisfied with Joyent's Advisory board, and by Node's lack of releases, core team member Fedor Indutny set up io.js.
-
ZURB Releases a Framework for Creating Responsive Apps
ZURB, a web design company and creator of Foundation (for Sites), has announced and open sourced another framework called Foundation for Apps (FA). FA provides HTML5/JavaScript tools for creating responsive web applications for desktop and mobile devices.
-
Netflix Burned by Express.js
Yunong Xiao, a Software Engineer at Netflix, recently wrote in the company's official tech blog about the latency problems that his team faced while working to move Netflix website UI to Node.js. In the post, he described the complex engineering process used to find out the root cause and how it lead to the decision of substituting the underlying API framework.