Business planning ideas from around the internet.
Publishing documents on edocr is a proven way to start demand generation for your products and services. Thousands of professionals and businesses publish marketing (brochures, data sheets, press releases, white papers and case studies), sales (slides, price lists and pro-forma agreements), operations (specifications, operating manuals, installation guides), customer service (user manuals) and financial (annual reports and financial statements) documents making it easier for prospects and customers to find content, helping them to make informed decisions. #SEO #leadgen #content #analytics
About edocr
I am an accomplished content marketing professional helping you to build your brand and business. In my current role, I fulfill a multi-faceted solution marketplace including: publishing and sharing your content, embedding a document viewer on your website, improving your content’s search engine optimization, generating leads with gated content and earning money by selling your documents. I gobble up documents, storing them for safekeeping and releasing the text for excellent search engine optimization, lead generation and earned income.
Publishing documents on edocr.com is a proven way to start demand generation for your products and services. Thousands of professionals and businesses publish marketing, sales, operations, customer service and financial documents making it easier for prospects and customers to find content, helping them to make informed decisions.
Get publishing now!
DETAILED REPORT OF FINDINGS
May 2018
Node.js is emerging as a universal development framework for digital
transformation with a broad diversity of applications.
With nearly 10 million Node.js users, three in four users are planning to increase
their use of Node.js in the next 12 months. Node users continue to report
positive business impact, including improving developer productivity and
satisfaction and lowering cost.
2
Major highlights
1.
Node.js is continuing to have a positive impact on users particularly around developer productivity and satisfaction;
when asked to describe Node.js, respondents use mostly positive terms like "fast", "easy", "awesome", "powerful",
"flexible" and even "fun".
2.
The coming year will likely see continued growth for Node.js. Most users expect to increase their usage, particularly in
Latin America and EMEA.
3.
A differentiated strategy by region may be called for given Node's global presence and the varying needs and
approaches by region. Among other things, there are key differences in business profile, deployment locations,
language & resource usage, priorities (e.g., around package managers or LTS), educational needs and experiences, all
of which may call for different approaches worldwide.
4.
It is becoming increasingly important to users to manage different packages for multiple environments but having
access to multiple registries is not particularly important outside Latin America. npm is by far the most widely used
package manager, but Yarn is gaining in popularity in many segments.
5.
Recent improvements around education have registered with users as evidenced by improved scores for ease of
learning Node.js, and for the availability and quality of resources. But more could be done, particularly in meeting the
needs of some segments (APAC, EMEA and new users) and in some topic areas (Managing Node.js in Production and
Node.js and Security).
3
EXECUTIVE SUMMARY
EMEA
44%
US / Canada
32%
Latin / South
America
7%
APAC
18%
SOURCE: Q4, Q7
4
International presence
BUSINESS / PERSONAL PROFILE
46%
6%
6%
5%
4%
1%
English
Spanish
German
French
Portuguese
Mandarin
.
.
.
26%
10%
6%
6%
5%
4%
1%
Collectively, respondents span 100+ countries and speak at least 60 languages
Fewer than half consider English their primary language
PRIMARY LANGUAGE SPOKEN top mentions
WHERE RESIDE top mentions
Professional profile
BUSINESS / PERSONAL PROFILE
Typical respondent is a developer in a small (<100 employees) firm, with 5 years professional experience
Although many have 10+ years total development experience, respondents are somewhat less experienced
overall in this wave
5
11%
25%
64%
Other
Manager
Developer / Tech
Developer / Tech
Software Engineer*
23%
Backend Engineer
9%
Frontend Engineer
8%
Sr. Backend Engineer
8%
Sr. Frontend Engineer
6%
Hobbyist programmer
4%
Manager
Tech Lead
9%
Architect
6%
C Level*
5%
Engineering Director
2%
Engineering Manager
2%
Other
Student / intern
7%
Research / analyst
1%
60%
19% 8% 13%
# EMPLOYEES
IN COMPANY
48 ee's
33%
36%
31%
PROFESSIONAL
DEVEL. EXPERIENCE
5.3 yrs
<3 yrs
3-9 yrs
10+ yrs
TOTAL
DEVEL. EXPERIENCE
19%
38%
43%
8.3 yrs
<3 yrs
3-9 yrs
10+ yrs
Median
<100
100-
999
1K-
4.9K 5K+
PROFESSIONAL TITLE
DEMOGRAPHICS
Experience with Node.js
SOURCE: Q17, Q20, Q21
6
NODE.JS USAGE PROFILE
The typical respondent has
been using Node.js for just
over 2 years, and spends
more than half of their
development time with
Node.js
YEARS USING NODE.JS
% OF TIME SPENT USING NODE.JS medians
% of Professional
Development Time
% of Total
Development Time
55%
60%
43%
23%
35%
< 2 yrs
2 - <3 yrs
3+ yrs
Median Years
2.3
Business impact
NODE.JS IMPACT & GETTING INVOLVED
As last year, many users say that Node.js has had a positive impact on their business chiefly through increased
developer productivity and satisfaction
Reduced development costs and increased application performance are also important outcomes tied to Node.js
Perhaps not surprisingly, longer-tenured users are far more likely than novices to report an impact from Node.js
SOURCE: Q54
7
68%
62%
56%
48%
24%
22%
13%
7%
6%
Increased developer productivity
Improved developer satisfaction
Reduced development costs
Increased application performance
Increased up time
Helped recruit developers
Helped increase customer satisfaction
Helped increase customer engagement
No impact
< 2 yrs 2+ yrs
Increased developer productivity 58%
74%
Improved developer satisfaction 51
68
Reduced development costs 45
62
Increased application performance 42
51
Increased uptime 19
27
Helped recruit developers 15
27
No impact
9
4
HOW NODE.JS HAS IMPACTED YOUR BUSINESS
IMPACT BY YEARS USING NODE.JS top impacts
32%
21%
11%
8%
5%
5%
1%
1%
Amazon Web Services
On-Premise Infrastructure
Heroku
Digital Ocean
Google Cloud Platform
Microsoft Azure
IBM Bluemix
Red Hat Openshift
29%
21%
12%
6%
4%
3%
1%
1%
Where code is deployed
NODE.JS USAGE PROFILE
AWS is the primary place where respondents deploy code for production, and it seems to be growing for use in development
On-Premise infrastructure is also widely used, but has dropped for use in production since last year
SOURCE: Q28, Q29, Q30
8
Primary
49%
33%
25%
21%
16%
11%
3%
3%
Total
Primary
FOR PRODUCTION
FOR DEVELOPMENT
On-Premise Infrastructure
Amazon Web Services
Heroku
Digital Ocean
Microsoft Azure
Google Cloud Platform
IBM Bluemix
Red Hat Openshift
Web Apps
Enterprise
Hobbyist
Big Data/Analytics
Embedded Systems
Mobile Apps
Games / gaming
Tooling Automation
Types of development work
NODE.JS USAGE PROFILE
Majority are spending time developing
web apps, particularly in full stack or
front-end positions
A notable minority also engage in
enterprise and/or hobbyist work
Those outside the traditional
development areas are more likely to be
working on embedded systems
SOURCE: Q24
9
85%
43%
36%
13%
8%
1%
1%
1%
<
<
<
Back-End
Full Stack
Front-End
Other
Web Apps
82%
92%
89%
66%
Enterprise
47
43
35
40
Hobbyist
32
41
35
37
Big Data/Analytics
13
14
7
13
Embedded Systems
8
7
3
19
Hobbyist ONLY
2
2
3
10
TYPE OF WORK by primary development focus
TYPES OF DEVELOPMENT WORK SPEND TIME ON top mentions
Databases
Front-end Frameworks / Libraries
Node.js Frameworks
Load Balancing
Containers / Cloud Native
CI
Messaging Systems
Tools / technologies used
NODE.JS USAGE PROFILE
A range of tools are used with Node.js,
primarily: databases, libraries, and
Node.js frameworks
Back-End and Full Stack developers most
likely to use a range of tools
Messaging systems and CI are less
commonly used than other tools and
usage has dropped since last year
SOURCE: Q27 (net categories)
10
96%
87%
82%
62%
58%
41%
15%
Back-End
Full Stack
Front-End
Other
Databases
98%
97%
89%
92%
Front-end Frameworks
83
93
94
69
Node.js Frameworks
84
90
67
59
Load Balancing
65
68
48
44
Containers / Cloud
62
61
48
45
CI
40
45
40
27
Messaging
21
15
4
12
TYPES OF TOOLS / TECHNOLOGIES USED WITH NODE.JS in past 12 months
TYPES OF TOOLS by Primary Development Focus
23%
20%
8%
3%
1%
48%
20%
12%
9%
4%
48%
34%
15%
8%
1%
73%
21%
13%
11%
8%
53%
41%
26%
26%
21%
67%
62%
40%
39%
34%
Front-End
Frameworks
Node.js
Frameworks
Load
Balancing
Containers /
Cloud Native
CI
Messaging
Systems
Databases
Tools / technologies used
NODE.JS USAGE PROFILE
A range of tools are used, though one or two tools dominate within each category
Usage of many tools has dropped while some have increased, including Angular 2, Vue, GraphQL, Docker and Kubernetes
SOURCE: Q27
11
<
13%
3%
1%
1%
<
Jenkins
Travis
Circle
Codeship
Shippable
Docker
AWS
Lambda
Kubernetes
Google Cloud
Func*
Azure
Functions
Nginx
Pm2*
Apache
HTTP*
HA Proxy
Apache
Traffic Sv
Express
GraphQL
Hapi
KOA
Restify
React
jQuery
Angular
Angular2
Vue
JSON File
Mongo DB
MySQL
Redis
PostgreSQL
RabbitMQ
ZeroMQ
ActiveMQ
NSQ
SPECIFIC TOOLS / TECHNOLOGIES USED in past 12 months
MAC OS
Windows
Ubuntu
Debian-based
Linux Distr
Enterprise
Linux & Fedora
Arch Linux
41%
24%
21%
5%
3%
3%
4%
12%
39%
21%
14%
2%
Primary OS / Distro
NODE.JS USAGE PROFILE
Ubuntu is the primary OS / Distro used in production,
while MAC OS is primary in development
Use of Windows in both production and
development has increased since last year,
particularly in US/CA, EMEA and in smaller companies
(among other segments).
SOURCE: Q41, Q42
12
In Production
In Development
PRIMARY OS / DISTRO USED top mentions
Languages used
SOURCE: Q25, Q33
13
LANGUAGES USED
3 other languages are used
on average besides Node.js
typically JavaScript and
then Python, Java or PHP
More than a third are using
ES2017 or above
OTHER LANGUAGES USED (PAST 12 MONTHS)
PRIMARY JAVASCRIPT LANGUAGE VERSION (6 MONTHS)
JavaScript
Python
Java
PHP
.Net
C++
Go
C
Ruby
Swift
93%
37%
35%
31%
20%
16%
16%
15%
14%
9%
27%
32%
35%
6%
ES2017
or above
ES2016
ES2015 (ES6)
or below
Don't
know
90%
76%
71%
70%
57%
53%
50%
42%
40%
31%
31%
29%
23%
20%
Rust
Node
Go
JavaScript
Swift
Scala
Python
C++
R
C
Java
.net
PHP
Ruby
Expected change in other languages
LANGUAGES USED
Use of other languages will also increase among current users including Rust, Go, and JavaScript
Usage of PHP and Ruby appears to be on the decline although many of those in Asia/Pacific plan
to increase their usage of PHP
SOURCE: Q25, Q26, among those who use respective brand and who provided an answer
14
Decrease
3%
3%
10%
3%
18%
21%
16%
23%
24%
28%
38%
33%
48%
43%
Increase
Use Now
6%
100%
16%
93%
9%
4%
37%
16%
5%
15%
35%
20%
31%
14%
EXPECTED CHANGE IN USE OVER NEXT 12 MONTHS among users of each language*
Other languages used in addition to Node.js
LANGUAGES USED
Language usage varies somewhat by region and development focus
PHP is less popular in US / CA and among those outside of traditional programming areas
Despite being less likely to use JavaScript and PHP, those "other" developers use more
languages on average (closer to 4), including C++ and C
SOURCE: Q25 Top mentions in past 12 months
15
US / CA
Full Stack
Front-End
Other
JavaScript
93%
93%
89%
96%
Python
39
35
35
39
Java
34
36
30
48
PHP
23
37
29
38
.Net
22
20
19
19
C++
20
16
13
8
Go
18
14
15
20
C
16
13
15
15
Ruby
20
12
8
11
Average #
3.3
3.2
2.8
3.3
Back-End
Full Stack
Front-End
Other
JavaScript
92%
95%
94%
84%
Python
36
38
33
41
Java
36
34
35
39
PHP
31
35
29
21
.Net
21
19
21
26
C++
15
15
13
33
Go
17
17
11
15
C
15
13
10
28
Ruby
12
14
14
16
Average #
3.2
3.2
2.9
3.6
BY REGION
BY PRIMARY DEVELOPMENT FOCUS
Package manager usage
PACKAGE MANAGERS
npm is, by far, the most widely used
package manager but Yarn is
gaining in popularity in many
subgroups
Respondents search for packages
almost entirely on npmjs.org or
through Google / search engine,
which are gaining popularity in APAC
and among other developers
SOURCE: Q47/Q48 (including blank/no answer)
16
60%
13%
1%
1%
1%
<
38%
32%
1%
1%
1%
1%
<
<
PACKAGE MANAGER USAGE
WHERE PACKAGES ARE SEARCHED FOR
npmjs.org
Google /
other search engine
npmS.IO / npm
npmsearch.com
StackOverflow /
other commun.
GitHub
npm
Yarn
Bower
JSPM
Duo
Informal coding education
SOURCE: Q18 *Single response question, but allowed multiple responses in 'other specify' in 2017; not trendable
17
LEARNING NODE.JS
The primary way
respondents are gaining
informal coding education
is via online courses
without an instructor
particularly outside US/CA.
While not widely used,
tutoring is more popular in
APAC than in other regions.
38%
9%
4%
5%
2%
2%
2%
31%
Online course (no instructor)
NodeSchool
Tutoring
Node.js meetup workshop
Udemy
Books / reading
Self-taught
None / no answer
INFORMAL CODING EDUCATION
Google / YouTube
NodeBots
Code School
Code Academy
Coding Bootcamp
Online tutorials
NodeTogether
NodeGirls
Node.js documentation
PluralSight
github
Freecode Camp
Blogs/articles
OTHER SOURCES mentioned by 1% or fewer
Node.js Skills Acquisition
LEARNING NODE.JS
Nearly all respondents learned Node.js in English which is non-native for more than half of respondents
In certain regions including EMEA and (especially) Latin America a vast majority of respondents learned
Node.js in a non-native language
SOURCE: Q7/Q8
18
53%
57%
51%
56%
48%
8%
77%
57%
97%
2017
Back-end
Full Stack
Front-end
Other
US/CA
EMEA
APAC
Lat Amer
PRIMARY DEV. FOCUS
REGION
98%
99%
99%
99%
91%
97%
97%
97%
100%
TOTAL
Learned in
English
LEARNED NODE.JS IN NON-NATIVE LANGUAGE
Ease of learning Node.js
LEARNING NODE.JS
About half of respondents say it was generally easy to learn. Very few complain that it is difficult
Surprisingly, those in Latin America who are most likely to have learned in a non-native language
are particularly upbeat about ease of learning
Newer users are less enthusiastic than those using it 2+ years suggesting that more could be
done to improve the learning experience
SOURCE: Q34, among those with an opinion; blanks excluded. * Top 3/Bottom 3 box on scale from 1 'extremely difficult' to 10 'extremely easy'.
49%
50%
51%
42%
47%
47%
50%
46%
58%
43%
54%
2017
Back-end
Full Stack
Front-end
Other
US/CA
EMEA
APAC
Lat Amer
< 2 yrs
2+ yrs
3%
2%
3%
4%
10%
3%
4%
2%
4%
4%
3%
PRIMARY DEV. FOCUS
REGION
TOTAL
YRS USING NODE.JS
Difficult
Easy
19
EASE OF LEARNING NODE.JS by subgroup
Resources used
LEARNING NODE.JS
Respondents use many resources
when learning a new language
documentation and StackOverflow
chief among them
Tutorial videos are also
widely used
While documentation and
StackOverflow are still top, newer
Node.js users are more likely than
others to also use free & paid
online courses and tutorial videos
SOURCE: Q37, among those who provided a response (no answer excluded) *Not trended by subgroup
20
84%
72%
58%
56%
40%
28%
25%
18%
15%
15%
12%
11%
Meet-up coding events
Workshops (independ-ent of conf's)
Enterprise tooling
Enterprise services
Biz case study podcasts
Biz case study webinars
< 2 yrs
2+ yrs
Documentation
80%
88%
StackOverflow
71
72
Free online courses
66
52
Tutorial videos
62
52
Publications
39
40
Paid online courses
35
24
Conference talk videos
19
29
Technical podcasts
16
19
Meetup talk events
10
17
Conferences
11
18
Documentation
StackOverflow
Free online courses
Tutorial videos
Publications
Paid online courses
Conference talk videos
Technical podcasts
Meet-up talk events
Conferences
Technical webinars
Case studies
RESOURCES RELY ON MOST WHEN LEARNING NEW LANGUAGE
/ FRAMEWORK / RUNTIME ENVIRONMENT
OTHER RESOURCES used by 8% or less
RESOURCES USED BY YEARS using Node.js
Methodology
BACKGROUND
This report presents selected findings from the 2018 Node.js User Survey.
The primary objective of the research was to profile Node.js users and identify potential areas of
improvement. The findings will be used for program development, marketing and PR/external
communications.
The study was conducted online from Oct 5, 2017 to January 7, 2018 via a self-administered
survey.
The survey was fielded worldwide in English and Chinese to encourage maximum response.
The survey link was distributed by the Node.js Foundation through a number of channels
including email, Twitter, conferences, blogs and word of mouth (meet-ups).
A total of 1,626 individuals responded to at least some questions in the survey.*
To ensure data integrity and unbiased interpretation, data analysis and reporting was conducted
by Research Collaborative, an independent market research firm.
Numbers may not total to 100% due to rounding
* Due to skip logic or missed questions, the number of responses for individual questions may be considerably lower
21
Thank you
For more information:
Contact [presenter]
+1 (xxx) xxx-xxxx
xxxxxxxx@yyyyy.zzz
22
2019 NODE.JS USER STUDY
DETAILED REPORT OF FINDINGS
May 2018
Appendix
Overview / methodology
BACKGROUND
This report presents selected findings from the 2018 Node.js User Survey.
The primary objective of the research was to profile Node.js users and identify potential areas of
improvement. The findings will be used for program development, marketing and PR/external
communications.
The study was conducted online from Oct 5, 2017 to January 7, 2018 via a self-administered
survey.
The survey was fielded worldwide in English and Chinese to encourage maximum response.
The survey link was distributed by the Node.js Foundation through a number of channels
including email, Twitter, conferences, blogs and word of mouth (meet-ups).
A total of 1,626 individuals responded to at least some questions in the survey.* ^
To ensure data integrity and unbiased interpretation, data analysis and reporting was conducted
by Research Collaborative, an independent market research firm.
Numbers may not total to 100% due to rounding
* Due to skip logic or missed questions, the number of responses for individual questions may be considerably lower. ^ For a population of 10M, a sample size of 384 is needed for a confidence
level of 95% and confidence interval of +/- %5. See https://www.surveysystem.com/sscalc.htm
24
Business / personal profile
SECTION HIGHLIGHTS
As with last year, the typical Node.js user is male, age 31 and college
educated.
A majority are developers, in small (<100 employees) companies, with 5+
years of professional development experience.
Although many have 10+ years total development experience, this year's
respondents are less experienced in terms of total development experience.
Respondents come from across the globe, but most are in US/CA or EMEA.
Collectively, respondents speak over 60 languages, but for nearly half
English is primary.
The mix of countries has changed somewhat since last year with fewer
from US and China and more from India and Canada.
There are considerable differences in personal and business characteristics,
with those from US/CA older, more experienced, and from larger companies
than users elsewhere.
25
Personal characteristics
BUSINESS/PERSONAL PROFILE
The typical Node.js user is male, age 31, college educated and white.
Respondents are slightly older in this wave, but gender and education are unchanged.
SOURCE: Q9, Q10, Q11, Q14 * Ethnicity asked as open end this year, closed end last year; not trendable
26
22%
46%
32%
31.0
< 25
25-34
35+
Male
94%
Female
5%
Other
1%
62%
18%
5%
5%
White/
Caucasian
Asian
Black/
African American
Hispanic/
Latino
RESPONDENT AGE
ETHNICITY*
Median Age:
High school or less
16%
Some college
10%
College degree
51%
Grad degree
21%
Other
2%
GENDER
EDUCATION
Profile by region
BUSINESS/PERSONAL PROFILE
There are notable differences in business and personal profile by region.
Those in the US/CA are older, more experienced and work in larger companies than their peers around the globe.
EMEA respondents are particularly highly educated.
The profile of APAC respondents has changed in many respects vs. last wave perhaps not surprising given the drop in
China as a percentage of APAC respondents this year. APAC respondents are relatively new to development.
SOURCE: Q1, Q3, Q7, Q9, Q14. Q15
27
US/CA
EMEA
APAC
LatAm
Co size (median # ee's)
99
24
24
40
Prof'l dev experience (median yrs)
7.5
5.3
3.7
4.4
Prof'l dev experience (10+ yrs)
42%
29%
18%
28%
Developers
60%
67%
64%
70%
Managers
29%
23%
24%
24%
US/CA
EMEA
APAC
LatAm
English primary language
92%
21%
42%
1%
Age (median)
33
31
29
30
Age (% 35+)
41%
31%
20%
24%
Male
91%
95%
97%
96%
Have grad degree
15%
28%
20%
8%
BUSINESS CHARACTERISTICS by region
PERSONAL CHARACTERISTICS by region
Node.js usage profile
SECTION HIGHLIGHTS
As with last year, the typical user has been working with Node.js over 2 years, and
spends more than half of his development time using it. The vast majority are
developing web apps.
Most respondents are primarily back-end or full stack development-focused, and
they use Node.js more regularly at work than others do.
Relatively few users are primarily focused on "other" non-traditional development
areas*, but those who are tend to be older and more highly educated than others.
Users are deploying through a range of channels, but AWS is most widely used for
production and On-premise or AWS for development. Heroku seems to be growing
in popularity in APAC and Latin America.
More than 4 in 5 back-end and full stack developers are using Node.js frameworks;
Express is tops, but Graph QL is increasingly prevalent this wave.
Most are using a transpiler and module bundler (especially full stack and front-end
developers). Babel is the preferred transpiler, but Typescript is growing. Webpack
continues to dominate the module bundler space.
Ubuntu is the primary OS/Distro used in production, and MAC OS in development
but Windows seems to be growing in popularity for both (especially in US/CA and
EMEA).
28
*Including DevOps, Desktop Apps, Mobile, IoT and Security
Back-end (including APIs)
Full Stack
Front-end
Ops/DevOps
Desktop Applications
Mobile
IoT
Security
37%
39%
14%
2%
2%
2%
2%
1%
Development focus
NODE.JS USAGE PROFILE
Three in four Node.js users are focused primarily on back-end or full stack development
There has been a slight drop in this wave in those who have any focus on back-end development
US / CA respondents are more focused on full stack than back-end
Ops / DevOps is really only a focus in US / CA although even here, it is not widely focused on
SOURCE: Q22, Q23
29
Primary Focus
69%
61%
49%
22%
19%
20%
12%
6%
NET Focus
US/CA EMEA
APAC
LatAm
Back-end
32%
38%
43%
42%
Full Stack
42
39
38
41
Front-end
15
14
13
11
Ops / DevOps
3
1
<1
1
Desktop Apps
2
2
2
1
Mobile
2
2
2
2
IoT
1
2
1
2
Security
<1
1
<1
0
Primary Development Focus by Region
<
DEVELOPMENT FOCUS title
PRIMARY DEVELOPMENT FOCUS by region
Profile by development area
NODE.JS USAGE PROFILE
There are some differences in users' business and personal characteristics based on development focus.
Full stack developers have been using Node.js the longest, and along with back-end developers, spend the most time with it.
Those outside of the three traditional development areas tend to be older and more highly educated than others.
SOURCE: Q1, Q3, Q4, Q7, Q9, Q10, Q15, Q17, Q20
30
Back-
end
Full
Stack
Front-
end
Other
Co size (median # ee's)
54
37
79
44
Prof'l dev experience (median yrs)
4.7
6.0
5.6
6.1
Prof'l dev experience (10+ yrs)
31
32
29
38
Developers
69% 61%
71%
50%
Managers
25% 28%
19%
32%
Years using Node.js (median)
2.2
2.5
2.3
2.2
% Prof Dev time Use Node.js
(median)
61% 62%
27%
39%
Back-
end
Full
Stack
Front-
end
Other
English primary language
43% 48%
44%
48%
Age (median)
31
31
31
35
Male
94% 95%
95%
91%
Have grad degree
22% 19%
18%
29%
US/CA
27% 34%
35%
39%
EMEA
46% 43%
45%
45%
APAC
19% 16%
15%
10%
Latin America
8%
8%
6%
4%
"Other" includes: Ops/Dev Ops, Desktop
Applications, Mobile, IoT and Security
BUSINESS CHARACTERISTICS by primary development focus
PERSONAL CHARACTERISTICS by primary development focus
Where deploy code
NODE.JS USAGE PROFILE
EMEA respondents are less likely than others to use AWS, preferring on-premise infrastructure.
US/CA respondents are also likely to be deploying via on-premise infrastructure
Heroku is growing in both APAC and Latin America, and is one of the top choices for
deployment for development in Latin America
SOURCE: Q28, Q30 ^ Attribute wording change; interpret trend cautiously * Items added to pre-list in 2017; not trended
31
For Production
For Development
US/CA
EMEA
APAC
LatAm
Amazon Web Services
37%
23%
42%
40%
On-Premise Infrastructure
20
27
11
12
Heroku
11
11
12
16
Digital Ocean*
7
9
7
7
Google Cloud
4
5
5
6
Microsoft Azure^
5
4
7
5
IBM Bluemix
2
1
1
3
Red Hat Openshift^
1
1
2
1
Depl not req'd
5
7
4
4
US/CA
EMEA
APAC
LatAm
On-Premise Infrastructure
32%
32%
20%
22%
Amazon Web Services
24
17
27
20
Heroku
9
12
16
20
Digital Ocean*
5
6
7
5
Google Cloud
3
4
4
1
Microsoft Azure^
3
4
7
4
IBM Bluemix
1
1
1
4
Red Hat Openshift^
1
1
1
1
Depl not req'd
16
16
14
13
WHERE PRIMARILY DEPLOY NODE.JS CODE by region
Where deploy code
NODE.JS USAGE PROFILE
Deployment also varies somewhat based on development focus.
AWS is widely used by back-end, full stack and front-end developers, but less so for others.
Heroku is relatively popular among full-stack developers.
SOURCE: Q28, Q30 ^ Attribute wording change; interpret trend cautiously * Items added to pre-list in 2017; not trended
32
Back-end Full Stack Front-end Other
Amazon Web Services
36%
33%
29%
16%
On-Premise Infrastructure
23
20
24
20
Heroku
10
14
9
8
Digital Ocean*
5
11
8
5
Google Cloud
5
5
4
5
Microsoft Azure^
5
4
4
9
IBM Bluemix
2
1
0
3
Red Hat Openshift^
1
1
1
2
Depl not req'd
4
3
13
13
Back-end Full Stack Front-end Other
On-Premise Infrastructure
29%
29%
33%
25%
Amazon Web Services
24
22
17
10
Heroku
12
14
9
7
Digital Ocean*
3
8
7
4
Google Cloud
3
4
2
4
Microsoft Azure^
5
3
2
7
IBM Bluemix
1
1
1
2
Red Hat Openshift^
1
1
1
2
Depl not req'd
15
12
20
27
For Production
For Development
WHERE PRIMARILY DEPLOY NODE.JS CODE by primary development focus
Transpilers and bundlers
NODE.JS USAGE PROFILE
Most respondents use a transpiler and module bundler particularly front-end and full stack developers.
Use of transpilers has risen since last year; Babel is most common, but use of Typescript is on the rise.
Webpack seems to be solidifying its notable lead among module bundlers.
SOURCE: Q31, Q32
33
69%
57%
78%
89%
47%
2017
Back-end Full Stack Front-end Other
PRIMARY DEV. FOCUS
USE A TRANSPILER
77%
69%
86% 93%
53%
2017
Back-end Full Stack Front-end Other
PRIMARY DEV. FOCUS
USE A MODULE BUNDLER
Primary OS / distro
NODE.JS USAGE PROFILE
Distro use varies somewhat by region, with Ubuntu more popular in APAC and Latin
America, and MAC OS more popular in US / CA
Debian-based Linux, while not widely used anywhere for development, is somewhat
popular in EMEA and Latin America in production
SOURCE: Q41, Q42
34
US/CA
EMEA
APAC
LatAm
6%
3%
3%
3%
12
12
14
3
37
37
45
41
14
26
16
28
16
11
15
17
3
3
2
1
US/CA
EMEA
APAC
LatAm
50%
35%
40%
33%
22
27
23
15
15
21
27
37
4
6
4
5
4
3
3
3
2
4
3
4
MAC OS
Windows
Ubuntu
Debian-based Linux
Ent. Linux & Fedora
Arch Linux
In Production
In Development
PRIMARY OS / DISTRO USED by region
Primary OS / distro
NODE.JS USAGE PROFILE
Primary distro varies somewhat by development focus
Ubuntu is most popular among back-end and full stack developers, while Windows is more popular
among front-end and "other" developers (where it is the #1 choice for both production and development)
SOURCE: Q41, Q42
35
Back-End Full Stack Front-End
Other
3%
3%
8%
6%
8
9
18
29
42
41
30
25
19
24
19
15
17
12
14
9
3
2
3
2
Back-End Full Stack Front-End Other
36%
47%
48%
26%
21
21
29
39
26
20
14
20
5
5
2
6
6
3
1
0
4
2
4
3
MAC OS
Windows
Ubuntu
Debian-based Linux
Ent. Linux & Fedora
Arch Linux
In Production
In Development
PRIMARY OS / DISTRO USED by primary development focus
Languages Used
SECTION HIGHLIGHTS
Node.js users are using a range of other languages besides Node.js more than
3 on average, including primarily JavaScript, Python, Java and PHP.
A third are using ES2017 or above three times as many as in last year.
APAC users use fewer languages on average than others, while those outside
traditional development areas use more particularly C++ and C.
Most expect to increase their use of Node.js over the next 12 months and the
number is rising. Growth will likely come from outside the US/CA particularly
in Latin America or EMEA.
Use of other languages is also expected to increase including Rust, Go and
JavaScript.
Usage of Ruby has dropped, and users are far more likely to say they will
"decrease" usage than increase over the next 12 months.
PHP is less popular in US/CA and among "other" developers; and, many of those
who use it say they will decrease usage over the next 12 months.
Go and Swift may be stealing the attention of Node.js users many of those
who plan to maintain/decrease with Node.js will increase with Go or Swift in the
next 12 months.
36
3%
2%
3%
3%
2%
4%
2%
3%
0%
Expected change in Node.js usage
LANGUAGES USED
Three quarters of respondents say they plan to increase their use of Node over the next 12 months up from 2016
The rise in increased usage is attributable to back-end developers and those in EMEA, although Latin American
respondents are most likely to say they will increase their usage
SOURCE: Q26, among Node.js users who provided an answer
37
76%
77%
74%
78%
75%
70%
77%
80%
88%
2017
Back-end
Full Stack
Front-end
Other
US/CA
EMEA
APAC
Lat Amer
Decrease
TOTAL
Increase
PRIMARY DEV. FOCUS
REGION
Stay same
22%
21%
24%
19%
22%
27%
21%
17%
12%
EXPECTED CHANGE IN USE OF NODE.JS OVER NEXT 12 MONTHS by subgroup
t
ange in
e.js usage
ES USED
r
quarters of respondents say they plan to increase their us of Node over the next 12 months up from 2016
The rise in increased usage is attributable to back-end developers and those in EMEA, although Latin American respondents
are most likely to say they will increase their usage
.j sers who provided an answer
r
I
r
I
S F NODE.JS VER NEXT 12 MONTHS by subgroup
2%
8%
3%
19%
19%
23%
43%
35%
37%
51%
3%
13%
3%
14%
26%
33%
38%
35%
49%
51%
3%
2%
13%
30%
30%*
35%
77%
76%
71%
43%
41%
41%
30%
28%
24%
18%
74%
70%
70%
53%
42%
30%
26%
31%
20%
24%
78%
72%
52%
34%
30%*
28%
Node
Go
JavaScript
Python
C++
C
Java
.net
Ruby
PHP
Expected change in other languages
LANGUAGES USED
Planned usage does not vary considerably across the three main developer segments except that back-end developers are
particularly likely to decrease their use of Java and front-end developers are less likely to decrease their use of PHP.
SOURCE: Q25, Q26, among those who use respective brand and who provided an answer * Sample size small (n<50) **Sample size too small to report (n<30)
38
Will increase
Will Decrease
**
**
**
**
**
**
**
**
Back-
End
Full-Stack
Front-End
EXPECTED CHANGE IN USE OVER NEXT 12 MONTHS among users of each language*
JavaScript 93%
Python 36%
Java 38%
PHP 35%
.Net 21%
C++ 15%
Ruby 14%
Go 14%
C 14%
Swift
9%
Rust
5%
JavaScript 94%
Python 40%
Java 30%
PHP 21%
.Net 21%
C++ 20%
Ruby 14%
Go 21%
C 16%
Swift
9%
Rust
8%
9%
14%
45%
57%
24%
23%
51%
10%
21%
23%
Expected change in other languages
LANGUAGES USED
Those who plan to increase their use of Node.js will be increasing their use of a number of other languages as well
Many of those who will hold steady/decrease with Node.js will be increasing their focus on Go or Swift
SOURCE: Q25, Q26, among those who use respective brand and who provided an answer
39
24%
76%
Expected Change
8%
33%
15%
8%
19%
26%
9%
67%
25%
50%
OTHER LANGUAGES: STEAD/DECREASE NODE.JS
Increase
Use of Node.js
Same/Decrease
Use of Node.js
Decrease
Increase
% Use
Expected Change
92%
56%
35%
27%
32%
48%
25%
72%
33%
60%
85%
OTHER LANGUAGES: INCREASE NODE.JS
Decrease
Increase
% Use
*
*
*
*
<1%
17%
36%
47%
36%
23%
42%
10%
30%
16%
4%
EXPECTED CHANGE IN USE OVER NEXT 12 MONTHS
Package Managers
SECTION HIGHLIGHTS
npm is by far the most widely used package manager, but Yarn is gaining in
popularity.
Node users search for packages primarily on ptmjs.org or Google/search
engines; the use of Google/search engines has increased since last year.
It is becoming increasingly important to users to manage different packages for
multi environments. Those in APAC and Latin American regions are most likely to
see this as a priority.
Availability of multiple registries is not widely seen as important in certain
segments like EMEA, US/CA and small companies.
Latin America is the only area where having multiple registries is an important
priority.
40
npmjs.org
'16
'17
Google/other search engine
'16
'17
NPMS.IO/NPM
'16
'17
npmsearch.com
'16
'17
StackOverflow/other commun.
'16
'17
GitHub
'16
'17
NPM
'16
'17
Yarn
'16
'17
Bower
'16
'17
JSPM
'16
'17
Duo
'16
'17
Package Manager Usage
PACKAGE MANAGERS
NPM is, by far, the most widely used package manager but Yarn is gaining in popularity in many subgroups.
Respondents search for packages almost entirely on npmjs.org or through Google/search engine, which are gaining
popularity in APAC and among other developers.
SOURCE: Q47/Q48 (including blank/no answer)
41
Package Manager Using
61%
60%
9%
13%
1%
1%
1%
1%
0%
1%
Where Search For Packages
<
<
27% did not
check anything
for either
question
35%
38%
28%
32%
3%
1%
2%
1%
1%
1%
1%
1%
Especially. . .
US/CA 64%
Yarn is growing across most regions . . .
US/CA
EMEA
APAC
LatAm
14%
14%
10%
12%
BckEnd FullStk
FrEnd
Other
13%
16%
19%
10%
. . .Within some development areas. . .
<100ees 100-999 1000+
13%
14%
13%
. . .And in smaller companies
Search engines are growing in APAC
US/CA
EMEA
APAC
LatAm
34%
31%
32%
31%
BckEnd FullStk
FrEnd
Other
36%
36%
39%
37%
. . .And other development areas
<
<
<
Managing different packages
PACKAGE MANAGERS
It is becoming increasingly important to be able to manage different packages for multi environments the rise most
evident among full stack developers and those in US / CA
These rises notwithstanding, managing different packages is particularly important to those in APAC and Latin America
SOURCE: Q49, among those with an opinion; blanks excluded. * Top 3/Bottom 3 box on scale from 1 'not at all important to 10 'extremely important'.
42
44%
44%
45%
44%
38%
41%
40%
52%
57%
2017
Back-end
Full Stack
Front-end
Other
US/CA
EMEA
APAC
Lat Amer
17%
18%
15%
15%
26%
20%
20%
8%
5%
TOTAL
Important*
Not Important*
PRIMARY DEV. FOCUS
REGION
IMPORTANCE OF MANAGING DIFFERENT PACKAGES FOR MULTI ENVIRONMENTS e.g., react vs react-native or cli
Availability of Multiple Registries
PACKAGE MANAGERS
The availability of multiple registries is not widely seen as important at least not outside Latin America.
EMEA respondents, and those in companies with fewer than 100 employees are least likely to value access to multiple
registries.
SOURCE: Q50, among those with an opinion; blanks excluded. * Top 3/Bottom 3 box on scale from 1 'not at all important to 10 'extremely important'. **Sample size small (n<50)
43
32%
33%
33%
30%
28%
32%
25%
40%
55%
27%
37%
38%
2017
Back-end
Full Stack
Front-end
Other
US/CA
EMEA
APAC
Lat Am**
<100
100-999
1000+
Not Important*
28%
26%
30%
26%
31%
30%
34%
18%
8%
31%
24%
24%
TOTAL
Important*
PRIMARY DEV. FOCUS
REGION
# EMPLOYEES
IMPORTANCE OF AVAILABILITY OF MULTIPLE REGISTRIES e.g., react vs react-native or cli
Learning Node.js
SECTION HIGHLIGHTS
The main way Node.js users learn a new language is through online courses without
an instructor, especially outside the US/CA
Nearly all users learned Node.js in English but for more than half, it was not their
native language.
EMEA and Latin American users are most likely to have learned in a non-native
language.
There has been a rise in those who say it is easy to learn Node.js, and improvement
in scores for availability and quality of resources in several topic areas.
Latin American users, despite having learned in non-native language, give
particularly high scores for availability, quality and overall ease of learning.
There are some differences perceptions by subgroup, with APAC and EMEA having
some concerns, and mid-size companies perhaps faring better than others.
Newer Node.js users are less enthusiastic about availability and quality of resources
than longer term users, although most are still positive.
Documentation and StackOverflow are the main sources users rely on when learning
a new language but free online courses and tutorial videos are also important and
something users would like more of (especially new users and those in Latin America.
44
JavaScript
General Node.js programming
ES2016 and beyond
Asynchronous programming
Node.js for front-end engineering
Managing Node.js in production
Node.js and security
Learning resources
LEARNING NODE.JS
There have been notable improvements in access to and/or quality of learning resources particularly for General Node.js
programming and Asynchronous programming
Still, more needs to be done to improve ratings for resources around managing Node.js in production and Node.js and
security for both areas, high negative scores are a red flag
SOURCE: Q35, Q36, among those who provided a rating. *Top 3/Bottom 3 on scale from 1 'poor e.g., impossible to find/access' to 10 'excellent e.g. easy to find/access'
^ Top 3/Bottom 3 on scale from 1 'poor' to 10 'excellent'
45
85%
74%
67%
51%
45%
25%
18%
1%
2%
2%
4%
6%
15%
25%
71%
64%
60%
46%
42%
28%
25%
2%
3%
4%
6%
8%
15%
21%
Availability
Poor*
Excellent*
Quality
Poor^
Excellent^
AVAILABILITY / QUALITY OF LEARNING RESOURCES
Learning resources
LEARNING NODE.JS
Perceptions of availability of resources vary considerably by region with those in Latin America generally
more upbeat, but those in APAC and EMEA having concerns in some specific topic areas
46
69% 69%
58%
70%
51% 50% 48%
61%
49%
45%
36%
47%
25% 22%
26%
39%
20%
14%
19%
31%
US/CA EMEA APAC LatAm
US/CA EMEA APAC LatAm
US/CA EMEA APAC LatAm
US/CA EMEA APAC LatAm
US/CA EMEA APAC LatAm
Poor*
2%
2%
3%
1%
4%
4%
7%
4%
5%
6%
11% 8%
16% 14% 19%
10%
24% 25%
30%
24%
Excellent*
SOURCE: Q35 among those who provided a rating. *Top 3/Bottom 3 on scale from 1 'poor e.g., impossible to find/access' to 10 'excellent e.g. easy to find/access'
ES2016 & Beyond
Asynchronous Programming
Node.js for Front-end Engineering
Managing in Production
Node.js & Security
AVAILABILITY OF LEARNING RESOURCES BY REGION selected resources
Learning resources
LEARNING NODE.JS
A similar pattern exists with regard to quality: Latin America respondents are
more pleased with quality while APAC and (less so) EMEA have concerns
47
63%
59%
53%
64%
49%
45%
41%
58%
43% 42%
34%
52%
29%
24%
33%
42%
26%
23% 24%
33%
US/CA EMEA APAC LatAm
US/CA EMEA APAC LatAm
US/CA EMEA APAC LatAm
US/CA EMEA APAC LatAm
US/CA EMEA APAC LatAm
4% 3% 4% 5%
6% 4% 9%
4%
8% 6% 9% 12%
17% 14% 16% 16%
20% 20%
25% 22%
Poor^
Excellent^
SOURCE: Q36 among those who provided a rating. ^Top 3/Bottom 3 on scale from 1 'poor' to 10 'excellent'
ES2016 & Beyond
Asynchronous Programming
Node.js for Front-end Engineering
Managing in Production
Node.js & Security
AVAILABILITY OF LEARNING RESOURCES BY REGION selected resources
Learning resources
LEARNING NODE.JS
Respondents in mid-size companies perceive greater access to some learning resources
than those in larger and smaller firms, but perceived quality is only marginally better
To the extent there has been an improvement in perceptions of availability of resources,
it's coming from midsize and smaller companies
48
65%
75%
68%
50%
59%
46%
24%
31%
21%
<100 100-999 1000+
<100 100-999 1000+
<100 100-999 1000+
Poor* 2% 1% 1%
5% 3% 5%
15% 16% 14%
Excellent*
SOURCE: Q35, Q36, among those who provided a rating. *Top 3/Bottom 3 on scale from 1 'poor e.g., impossible to find/access' to 10 'excellent e.g. easy to find/access'
^ Top 3/Bottom 3 on scale from 1 'poor' to 10 'excellent'
58%
65%
59%
45%
52%
46%
27%
33%
28%
<100 100-999 1000+
<100 100-999 1000+
<100 100-999 1000+
Poor^ 5% 3% 2%
7% 4% 4%
17%
14% 14%
Excellent^
Availability
Quality
# E M P L O Y E E S
# E M P L O Y E E S
# E M P L O Y E E S
# E M P L O Y E E S
# E M P L O Y E E S
# E M P L O Y E E S
ES2016 & Beyond
Asynchronous
Programming
Managing
in Production
Managing
in Production
ES2016 & Beyond
Asynchronous
Programming
AVAILABILITY / QUALITY OF LEARNING RESOURCES BY CO SIZE selected resources
Learning Resources
LEARNING NODE.JS
Newer Node.js users give lower scores than others on availability in several topic areas
While still low, their higher negative ratings are worthy of note
49
82%
87%
69%
78%
62%
71%
45%
55%
< 2 yrs 2+ yrs
< 2 yrs 2+ yrs
< 2 yrs 2+ yrs
< 2 yrs 2+ yrs
Poor*
1% 1%
4% 1%
3% 1%
6% 3%
Excellent*
SOURCE: Q35, Q36, among those who provided a rating. *Top 3/Bottom 3 on scale from 1 'poor e.g., impossible to find/access' to 10 'excellent e.g. easy to find/access'
NOT TRENDED BY SUBGROUP ^ Top 3/Bottom 3 on scale from 1 'poor' to 10 'excellent'
Poor^
Excellent^
YRS USING Node.js
YRS USING Node.js
YRS USING Node.js
YRS USING Node.js
73%
70%
61%
65%
57%
62%
46% 47%
< 2 yrs 2+ yrs
< 2 yrs 2+ yrs
< 2 yrs 2+ yrs
< 2 yrs 2+ yrs
3% 2%
5% 2%
6% 3%
8% 4%
YRS USING Node.js
YRS USING Node.js
YRS USING Node.js
YRS USING Node.js
<
Availability
Quality
JavaScript
Gen'l Node.js
Programming
Asynchronous
Programming
ES2016 &
Beyond
AVAILABILITY / QUALITY OF LEARNING RESOURCES BY USING NODE.JS selected resources
JavaScript
Gen'l Node.js
Programming
Asynchronous
Programming
ES2016 &
Beyond
Resources used
LEARNING NODE.JS
To the extent users want more learning resources, documentation, free online courses and tutorial videos top the list
Consistent with their current usage, new Node.js users are particularly likely to want free online courses and tutorial videos
50
Documentation
Free online courses
Tutorial videos
Case studies
Conferences
Meet-up coding events
Conference talk videos
Paid online courses
Technical podcasts
Meet-up talk events
Technical webinars
Enterprise tooling
Workshops (indep of confs)
Enterprise services
Biz case study podcasts
Biz case study webinars
Other Resources
(used by < 5%)
SOURCE: Q38, including no answers *Not trended by subgroup
< 2 yrs 2+ yrs
Documentation 33%
34%
Free online courses
42
27
Tutorial videos
30
25
Case studies
15
16
Conferences
12
16
Meet-up coding events
14
12
Paid online courses
14
10
Technical podcasts
12
12
34%
33%
27%
15%
14%
13%
12%
12%
12%
11%
10%
7%
7%
RESOURCES WOULD LIKE MORE OF top mentions
RESOURCES WOULD LIKE MORE OF BY USING NODE.JS* top mentions
Resources used
LEARNING NODE.JS
Latin American users are particularly open to new learning resources particularly around free
online courses, tutorial videos, conferences and (increasingly) conference talk videos
Front end developers are less likely than others (and than last wave) to want more meet-up events
SOURCE: Q38, including no answers
51
US/CA
EMEA
APAC
LatAm
34%
34%
34%
36%
32
31
36
46
27
24
30
39
14
12
15
29
11
16
22
21
13
10
17
17
11
9
14
17
15
10
12
17
12
10
11
22
Documentation
Free online courses
Tutorial videos
Conferences
Case studies
Meet-up coding events
Meet-up talk events
Technical podcasts
Conference talk videos
Back-End
Full Stack
Front-End
Other
40%
38%
35%
34%
39
38
38
35
31
35
27
23
18
18
12
10
19
17
16
15
16
15
9
13
13
14
8
10
18
14
10
7
14
13
11
12
By Region
By Primary Development Focus
RESOURCES WOULD LIKE MORE OF top mentions
Node.js Versions & LTS
SECTION HIGHLIGHTS
Most Node.js users use a version manager typically Nvm.
Just over half use LTS release line, but use of current release line is increasing
particularly among Full stack and "other" developers, and in smaller companies.
It is important to most users to have LTS for Node.js, although it is somewhat
less important to those in small companies or in EMEA.
There has been a drop in those who say the LTS schedule support timeframe is
'clear', down to just half of users. Those least likely to see as clear are front-end
developers, APAC and those in smaller companies.
New users are less likely to use a version manager, and are more likely to use
Apt-Get than their more seasoned peers.
Importantly, only a minority of new users report a good understanding of the
LTS schedule/support timeframe.
52
Release Line
SOURCE: Q39
53
NODE.JS VERSIONS & LTS
More than half of users rely
on LTS release line but
that number is slipping
Current is particularly
popular among small
companies, and newer
Node.js users
55%
43%
2%
2017
Current
LTS
Other
52%
12%
11%
9%
8%
5%
Nvm
Apt-get
N
Docker
Homebrew
Nvm-Windows
Version managers
NODE.JS VERSIONS & LTS
Three in four Node.js users say they use a Node.js version manager typically NVM
SOURCE: Q43
54
76%
Use Version
Manager
Nodenv
Nave
Nodebrew
Nodist
Other Version Managers
(used by 1% or less).
2017
USE A NODE.JS VERSION MANAGER
NODE.JS VERSION MANAGER USED top mentions, among those who use any
LTS support
NODE.JS VERSIONS & LTS
It is important to most users to have LTS for Node.js
Users in EMEA and smaller companies are less likely to see it as a priority, but even here, more than half say it is important
SOURCE: Q40, among those with an opinion; blanks excluded. * Top 3/Bottom 3 box on scale from 1 'not at all important' to 10 'extremely important' Question new in 2017/not trended
55
61%
65%
61%
54%
56%
65%
57%
62%
69%
57%
63%
70%
Total
Back-end
Full Stack
Front-end
Other
US/CA
EMEA
APAC
Lat Amer
< 100
100-999
1000+
Not important*
12%
10%
11%
16%
13%
10%
14%
9%
11%
13%
8%
9%
Important*
PRIMARY DEV. FOCUS
REGION
# EMPLOYEES
IMPORTANCE OF HAVING LONG TERM SUPPORT (LTS) FOR NODE.JS
LTS support
NODE.JS VERSIONS & LTS
While many say the LTS Schedule / Support timeframe is clear, that number has dropped
significantly since last year overall and across multiple segments
APAC users, front-end developers and those in small companies are least likely to see LTS
schedule / support timeframe as clear
SOURCE: Q45, Among those with an opinion (Blanks excluded) *Top 3/Bottom 3 box on scale from 1 'very confused' to 10 'perfectly clear'
56
51%
53%
51%
40%
57%
52%
54%
40%
57%
47%
57%
56%
2017
Back-end
Full Stack
Front-end
Other
US/CA
EMEA
APAC
Lat Amer
< 100
100-999
1000+
Confusing*
8%
5%
9%
10%
12%
8%
7%
11%
8%
10%
6%
5%
Clear*
PRIMARY DEV. FOCUS
REGION
# EMPLOYEES
IMPORTANCE OF LTS SCHEDULE / SUPPORT TIMEFRAME FOR VARIOUS VERSIONS by subgroup
Understanding newer Node.js users
NODE.JS VERSIONS & LTS
Newer Node.js users are less likely than their more seasoned peers in their use of version manager, and are more likely to use Apt-Get
While it is not as important to them to have LTS support, most novice users still do want it, and their understanding of the
schedule/support timeframe is weak
57
69%
80%
< 2 yrs
2+ yrs
SOURCE: Q40, Q43, Q45 * Top 3/Bottom 3 box on scale from 1 'not at all important' to 10 'extremely important'
NOT TRENDED BY SUBGROUP
^ Top 3/Bottom 3 box on scale from 1 'very confused' to 10 'perfectly clear'
YRS USING Node.js
NVM
48%
55%
Apt-Get
19%
8%
N
9%
12%
55%
66%
< 2 yrs
2+ yrs
Important*
Not important*
13%
10%
37%
60%
< 2 yrs
2+ yrs
11%
6%
Clear^
Confusing^
USE VERSION MANAGER
IMPORTANCE OF HAVING LTS FOR NODE.JS
UNDERSTANDING OF LTS SCHEDULE
/ SUPPORT TIMEFRAME
Node.js Impact & Getting Involved
SECTION HIGHLIGHTS
Users are very upbeat and excited about Node.js with words like "fast" "easy"
"awesome" "simple" "powerful" and "fun" widely used to describe Node.js
Node.js is continuing to have a positive impact on many users primarily
through increased productivity and satisfaction, reduced development costs and
increased app performance.
The impacts may not be immediately clear however: new users are less likely to
report positive impacts in many areas.
While it's not the most widely felt benefit, users in US/CA are more likely than
others to say Node.js.js has helped with recruiting.
Despite their positive perceptions, few have been contributing to open source
projects for Node.js.
There is growing interest in getting involved, however: nearly a third say they are
interested in contributing and nearly half say they might be open to mentoring
others (both up from last year).
Those most interested in being involved include users in Latin America, APAC,
and back-end and full stack developers.
The main barriers are time and inexperience but some Node.js users don't
know how to contribute, or feel the community is not welcoming.
58
Words to describe Node.js
NODE.JS IMPACT & GETTING INVOLVED
In their own words, respondents used
mostly positive adjectives to describe
Node.js
They particularly like that it is fast,
simple, easy, yet powerful and flexible.
SOURCE: Q53
59
Business impact
NODE.JS IMPACT & GETTING INVOLVED
Users in Latin America are particularly likely to note positive impacts
particularly around productivity, application performance and uptime
Node.js has helped with recruiting in the US/CA more than other regions
SOURCE: Q54
60
US/CA
EMEA
APAC
LAT AM
Increased developer productivity
68%
66%
69%
78%
Improved developer satisfaction
64
60
60
65
Reduced development costs
60
51
61
56
Increased application performance
43
47
53
63
Increased uptime
22
23
24
40
Helped recruit developers
34
18
18
12
No impact
7
6
3
3
HOW NODE.JS HAS IMPACTED YOUR BUSINESS top impacts
Groups working with
NODE.JS IMPACT & GETTING INVOLVED
Consistent with last year, relatively few Node.js users reports contributing to open source repositories
Github, npm and Express are most widely contributed to
SOURCE: Q19
61
10%
8%
6%
3%
3%
3%
https:/github.com/node.js
Npm
Express
Gulp
Lodash
Async
Request
NodeSchool
Browserify
I18n
Libuv
Streams
Nodebots
Node-serialport
2% or fewer mention. . .
Most Widely Mentioned:
...nodejs/nodejs.org
3%
...nodejs/LTS
2%
...nodejs/v8
2%
...nodejs/http2
1%
...nodejs/build
1%
...nodejs/node-gyp
1%
...nodejs/TSC
1%
OPEN SOURCE REPOSITORIES / GROUPS / PROJECTS IN NODE.JS CONTRIBUTE TO
Groups working with
NODE.JS IMPACT & GETTING INVOLVED
Users in Asia / Pacific region are more likely to contribute to many groups
62
US/CA
EMEA
APAC
LatAm
12%
7%
12%
9%
5
7
14
9
4
5
11
6
2
3
5
4
2
3
6
4
1
3
6
4
1
1
4
3
SOURCE: Q19
https:/github.com/node.js
Npm
Express
Gulp
Lodash
Async
Browserify
Back-End Full Stack Front-End Other
10%
10%
5%
12%
6
7
8
12
6
7
4
7
3
3
4
4
2
3
3
3
3
3
1
4
2
1
2
2
By Region
By Primary Development Focus
OPEN SOURCE REPOSITORIES / GROUPS / PROJECTS IN NODE.JS CONTRIBUTE TO
Interest in getting involved
NODE.JS FOUNDATION & GETTING INVOLVED
Encouragingly, there has been a rise in the number of Node.js users who are interested in contributing to the project and/or mentoring others
Those most interested in being involved include users in Latin America and APAC, and back-end and full stack developers
While time and lack of skill are, by far, the primary barriers to contributing, some are held back because they don't know HOW to contribute
SOURCE: Q58, Q59, Q60
63
31% Yes
45% Yes / Maybe
INTEREST IN CONTRIBUTING TO OPEN
SOURCE NODE.JS PROJECT
INTEREST IN MENTORING OTHERS