{"id":234,"date":"2016-09-16T17:14:45","date_gmt":"2016-09-16T17:14:45","guid":{"rendered":"http:\/\/redmonk.com\/fryan\/?p=234"},"modified":"2017-07-14T15:31:45","modified_gmt":"2017-07-14T15:31:45","slug":"language-framework-popularity-a-look-at-javascript","status":"publish","type":"post","link":"https:\/\/redmonk.com\/fryan\/2016\/09\/16\/language-framework-popularity-a-look-at-javascript\/","title":{"rendered":"Language Framework Popularity: A Look at JavaScript"},"content":{"rendered":"

TL; DR<\/strong> \u2013 Express is the biggest game in town by orders of magnitude. Early adopters are increasingly looking to Koa. Sails continues to grow in popularity.<\/p>\n

Framework: \u2018a basic structure underlying a system, concept, or text.\u2019<\/em><\/p>\n

We have recently\u00a0looked at frameworks used with Java<\/a>, and as we noted one of the factors which drives the popularity of a language is the availability of frameworks and tools which enhance developer productivity, something which Stephen O\u2019Grady<\/a>\u00a0has covered in the past<\/a><\/p>\n

In the bi-annual RedMonk Programming Language Rankings<\/a> produced by my colleague Stephen O\u2019Grady we consistently see JavaScript as one of the top three most popular languages. There are a number of factors that people point to, but the majority of growth in the usage of JavaScript in the language rankings is directly attributable to the growth in the usage in Node.js.<\/p>\n

While many developers can, and still do, argue that \u2018real programmers\u2019 don\u2019t use JavaScript, this is a demonstrably untrue statement in 2016. Companies such as Uber, Walmart, Disney and Paypal are running large parts of their mission critical, server side, infrastructure on JavaScript.<\/p>\n

Looking to the future we continuously hear of developers choosing JavaScript as their preferred language with respect to the emerging serverless paradigm<\/a>. The improvements, and gradual removal of some of the \u2018quirks\u2019 of the language, which are being driven by the ECMA process<\/a> all point towards an even stronger future for the language in multiple settings.<\/p>\n

For the purposes of this analysis we looked at the frameworks we hear mentioned most frequently in our conversations around JavaScript. These frameworks are primarily focused on the server side, with the criteria that we hear the framework mentioned in conjunction with creating REST APIs. This is by no means a fully exhaustive list, but it does capture the most popular frameworks that we hear about being used with JavaScript (some frameworks are layered together, with frameworks such as SailsJS, KrakenJS and FeathersJS all built on Express).<\/p>\n

There are a number of other incredibly popular JavaScript frameworks focused on other problem spaces that we have not included here, such as Socket.io, Derby and Meteor. Front end frameworks such as Angular and React are also outside the scope of this particular piece of research.<\/p>\n

If there is a framework you feel we should be looking at, either in this context, or in the wider JavaScript ecosystem, please do add a comment below or let me know on twitter<\/a>.<\/p>\n

Framework Popularity<\/h2>\n

We began our analysis by looking at the popularity of various frameworks on Github. Express emerged as the clear winner here.<\/p>\n

\"final-javascript-fw-stars-20160912\"<\/a><\/p>\n

\"final-javascript-fw-issues-20160912\"<\/a> \"final-javascript-fw-commits-20160912\"<\/a><\/p>\n

Next we looked at download stats from npmjs.org.
\n<\/a><\/p>\n

\"final-npm-wexpress-20160916\"<\/a><\/p>\n

It is here that the dominance of Express is really shown. At over 100 million cumulative downloads it is by far the most popular framework for use with JavaScript. The next closest competitor is HAPI, which has 3.3 million cumulative downloads. To put this in perspective Express got twice as many downloads in the month of August as HAPI has gotten in its entire lifetime. Now there are many factors that you should take into account, including upgrades, version iterations, dependencies, automated build systems and so forth. However, even taking all of these factors into account it is clear that, no matter what way you slice and dice the information, Express is the clear leader.<\/p>\n

Among the remaining frameworks we see the following breakdown of downloads.<\/p>\n

\"final-npm-woexpress-20160916\"<\/a><\/p>\n

Only a subset of the frameworks were represented on Twitter.<\/p>\n

\"final-avascript-fw-twitter-2016-09-16\"<\/a><\/h2>\n

Commerical and Community Contributions to\u00a0Individual Frameworks<\/h2>\n

Before we delve into the frameworks, we do have to note the outsized influence of TJ Holowaychuk<\/a> on both Express<\/a> and Koa<\/a>. He accounts for 75% and 44% of the code changes in the respective projects. It is fair to say that Node.js adoption would be nowhere near the level it is without his contributions. For this analysis all of TJ\u2019s contributions are marked as community.<\/p>\n

Express<\/h2>\n

Now while it is outside the scope of this analysis, it is impossible to talk about Express<\/a> and not acknowledge the frustrations which emerged in the community in recent times, from the sale of the Express name to Strongloop<\/a>, ultimately ending up in IBM, and a key maintainer leaving the project. There has been a defined drop off in commit activity over the last few years.<\/p>\n

\"final-javascript-express-cci-20160912\"<\/a>\"final-javascript-express-ccc-20160912\"<\/a><\/p>\n

 <\/p>\n

Ownership of Express moved from IBM to the Node Foundation in February of this year<\/a>. As of now there has not been a noticeable\u00a0uptick in activity.<\/p>\n

Koa<\/h2>\n

The original team behind Express are now focused on the Koa<\/a> framework. One of the key aspects of Koa is the decision to ditch callbacks in favour of generators<\/a>. Now this impacts adoption in some unusual ways. For many developers coming to Node, callbacks were and are one of the more difficult concepts to understand, and people often end up in \u2018callback hell\u2019. The trade-off is once the investment has been made to learn an approach, e.g. callbacks, people are sometimes reluctant to move on.<\/p>\n

\"final-javascript-koa-cci-20160912\"\"final-javascript-koa-ccc-20160912\"<\/a><\/p>\n

Developers we speak to that are using Koa are very much in the early adopter area, but we do expect to see significant further growth in the usage of Koa.<\/p>\n

Sails<\/h2>\n

Given our bias towards server side frameworks in this research, we debated including Sails<\/a> as it is primarily discussed as a front end technology. However, Sails is reasonably widely used for creating REST APIs, hence its inclusion.<\/p>\n

\"final-javascript-sailsjs-cci-20160912\"<\/a> \"final-javascript-sailsjs-ccc-20160912\"<\/a><\/p>\n

<\/h2>\n

Loopback<\/h2>\n

Loopback<\/a> is the opensource basis for IBM\u2019s API Connect product, and as you might expect IBM dominate the overall contributions to Loopback. Loopbacks focuses on making REST APIs easy to create and manage.<\/p>\n

\"final-javascript-loopback-cci-20160912\"<\/a> \"final-javascript-loopback-ccc-20160912\"<\/a><\/p>\n

 <\/p>\n

HAPI<\/h2>\n

HAPI<\/a> was originally created at Walmart, and is used in a number of large enterprises. There is still some growth in interest, and the community remains reasonably active.<\/p>\n

\"final-javascript-hapi-cci-20160912\"<\/a> \"final-javascript-hapi-ccc-20160912\"<\/a><\/p>\n

During 2015 a number of the main project leads, who collectively account for almost 88% of the code contributions to HAPI, moved onto other roles from Walmart, and we have taken this into account in our analysis. The project leads have stated they will continue to remain involved in HAPI.<\/p>\n

Kraken<\/h2>\n

The Kraken<\/a> framework was created at Paypal, and they remain by far the biggest contributor to the framework. The overall growth in interest appears to have tapered off at this point, as has them level of contributions from Paypal<\/p>\n

\"final-javascript-karkenjs-cci-20160912\"<\/a> \"final-javascript-karkenjs-ccc-20160912\"<\/a><\/p>\n

Feathers<\/h2>\n

Feathers<\/a> is included here due to the spike in interest we noted in early 2016. We have heard of some usage for the generation of \u201creal-time\u201d REST APIs using the framework.<\/p>\n

\"final-javascript-feathers-cci-20160912\"<\/a> \"final-javascript-feathers-ccc-20160912\"<\/a><\/p>\n

Commercial Support & Licensing Information<\/h2>\n

When we move to large scale enterprise deployments, commercial support can become a significant factor for software, although this appears to be far less of a concern among the JavaScript community. \u00a0The MIT License is used by all of the top tier frameworks analysed bar Kraken.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Framework<\/strong><\/td>\nCommercial Support<\/strong><\/td>\nLicense<\/strong><\/td>\n<\/tr>\n
Express<\/td>\nIBM<\/a><\/td>\nMIT License<\/td>\n<\/tr>\n
Sails<\/td>\nNone<\/td>\nMIT License<\/td>\n<\/tr>\n
Koa<\/td>\nNone<\/td>\nMIT License<\/td>\n<\/tr>\n
Loopback<\/td>\nIBM<\/td>\nMIT License<\/td>\n<\/tr>\n
HAPI<\/td>\nNone<\/td>\nModified MIT (not clearly stated)<\/td>\n<\/tr>\n
Kraken<\/td>\nNone<\/td>\nApache 2.0<\/td>\n<\/tr>\n
Feathers<\/td>\nNone<\/td>\nMIT License<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Notes on the analysis<\/strong><\/p>\n

    \n
  • Data was pulled to\u00a0the end of August<\/li>\n
  • Where possible we have identified commercial contributions to a project, but there will be some minor gaps and inaccuracies in this mapping.<\/li>\n<\/ul>\n

    Disclaimers:<\/strong> Meteor and IBM (owners of StrongLoop) are RedMonk customers.<\/p>\n","protected":false},"excerpt":{"rendered":"

    TL; DR \u2013 Express is the biggest game in town by orders of magnitude. Early adopters are increasingly looking to Koa. Sails continues to grow in popularity. Framework: \u2018a basic structure underlying a system, concept, or text.\u2019 We have recently\u00a0looked at frameworks used with Java, and as we noted one of the factors which drives<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,15,32,34,24],"tags":[],"class_list":["post-234","post","type-post","status-publish","format-standard","hentry","category-community","category-developers","category-frameworks","category-javascript","category-research"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/redmonk.com\/fryan\/wp-json\/wp\/v2\/posts\/234","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/fryan\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/fryan\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/fryan\/wp-json\/wp\/v2\/users\/40"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/fryan\/wp-json\/wp\/v2\/comments?post=234"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/fryan\/wp-json\/wp\/v2\/posts\/234\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/fryan\/wp-json\/wp\/v2\/media?parent=234"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/fryan\/wp-json\/wp\/v2\/categories?post=234"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/fryan\/wp-json\/wp\/v2\/tags?post=234"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}