Development of the AppJS project is terminated, then use node-webkit

A little more than a year ago (October 1, 2012), I posted on Habrahabr the blog recording “ Node.js + Chromium = AppJS: one of the promising options for the second step of the web developer’s evolution ”, which cited AppJS as an example of such a combination of Node.js and Chromium engines , which allows each web developer, using technologies familiar to him (JavaScript, HTML, CSS), to become a developer of applications with a GUI (graphical user interface), combining the expressive capabilities of the Chromium browser and the power of the API Node.

The next day (October 2, 2012), in the blog post “ Node.js + Chromium = node-webkit: an even more promising option for the second step of the web developer’s evolution ”, I pointed out that AppJS is not the only or even the best option: node-webkit is different convenience and greater API capabilities, more extensive documentation, and also ensures the launch of ZIP-packaged applications.

And what? - not even thirteen months passed, as the success of node-webkit became obvious for AppJS developers. Today, on Twitter at AppJS, you can read that the development of the AppJS project is discontinued, since node-webkit has achieved its goal:
')


This well-deserved victory of Intel's open source technology center (which is developing node-webkit) means the onset of such a long GUI uniformity for Node, which can be compared with the effect of the end of the “browser war” on the Web at one time. This will save developers from the problem of choice, but the engine itself may face the risk of stagnation in the absence of competitors.

True, the absence of close competitors (in the field of “Node + Chromium”) does not mean anything. More distant competitors are visible on the horizon, also aimed at creating GUI applications using web -based technology — for example, applications from Firefox OS (which, as jeston told us today, are able to work on Android, not just on Windows, Linux and Mac OS X) . And last month (in September 2013) and Google presented their own predecessor to them - these are Chrome Apps , which Yevgeny Zolotov in Computerre reviewed under the loud headline “ Chrome against all: will Microsoft and Apple replace Google’s browser? ".

Honestly, the Node API (in conjunction with the UI node node-webkit ) I like somewhat more than the Google Platform API and even WebAPI Firefox OS. Do you know why more? Because API Node provides for easy loading of modules - and from this idea, as from a seed, an extensive list of ready-made open source modules created by third parties, available for installation from the npm package warehouse and for later use, has grown.

And what in Google Apps and in Firefox OS can I put next to this?