February 26, 2016
After that, work on ECMAScript proceeded at a lower pace. Instead of taking a big bang approach, a steady evolution was set in motion. Transpilers (compilers that take modern ECMAScript and translate it to an older version of ECMAScript that browsers understand) were introduced, which meant that developers could start using new language features without having to wait for browser vendors to implement them.
Another exciting development is Electron. This lets you build hybrid apps for desktop. The user interface is built in HTML/CSS, while file and network I/O is done through Node APIs.
Basically, a platform consists of three parts, the engine being only one part of it: the infrastructure (Chrome, Node, Cordova, Electron, etc.) the UI (DOM, Alloy, Cocoa, etc.) the engine (e.g. V8)
Recently, we saw the rise of the MV* frameworks. The three that came out on top were: Backbone, Angular and Ember. Just like the PHP community is subdivided by developers that use Zend Framework, Symfony and Laravel, these MV* frameworks caused subcommunities to form.
- frameworks like React, Ember and Angular
- frameworks like PhoneGap (Cordova)
- front-end and UX
- web technology and full stack
- languages like CSS and HTML5
- languages like PHP
In 2007, Jeff Atwood proposed the following law:
It seems he was right. Although the reverse is probably true as well: