‎"What happens when — and this is inevitable — a generation completely comfortable with remix culture becomes a majority of the electorate, instead of the fringe youth? What happens when they start getting elected to office?"

The theme of my first talk next week at Le Web is the HTML5 Experience, because I want to emphasize that HTML5 (et al) is about Developer Experience as much as User Experience.

On UX, we know about all the hot toys - canvas, audio, chatroulette streaming etc. Most of this has led DX, but now DX is fighting back as an equally important part of the web programming movement.

Web development experience is undergoing disruption along several axes:

* JavaScript++ CoffeeScript, now the 13th most popular language on GitHub, and other languages are making life easier and letting developers experiment with features that may one day become standard. This is also true for HTML (Jade/HAML) and CSS (Less/SASS/Stylus). Meanwhile, JavaScript Proper itself is indeed coming along and picked up momentum in the past year with features such as generators and list comprehensions now part of the standard and will benefit from real-world experiments in advanced JavaScript syntax. See http://altjs.org/ for more info on the new breed of JavaScript++ languages.

* Web Intents I've seen some amazing reactions from Web Intents recently. One well-known webdev authority described it to me as "the next Ajax", someone at Appsworld told me it blew his mind. It's part of a broader movement which is closing down the traditional same-domain silo. And this may well beckon a revolution of componentization on the web comparable to the open source component revolution of the previous decade. See http://webintents.org for more info.

* Web Components This is the other type of componentization movement happening, which I saw +Alex Russell demo at last week's London JavaScript. There's a lot to it, but the bottom line of this proposal is that developers will be able to create new HTML elements, which could then be consumed easily by non-programmer types in their design and authoring pursuits, much as they can happily introduce paragraphs and divs today, but can't easily/robustly introduce third-party components such as date pickers. See http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html for more info.

There's more in the works too, e.g. shared workers, CSS4 parent selectors, JavaScript modules. Most of this isn't yet finalised, but it's clear that increased demands on complexity, due to all the new userland features of HTML5, are being met with improvements in the platform we build those features on.