Skip to content

Commit 15d692b

Browse files
marco-ippolitomarco-ippolito
authored
April 2024 Survey (#261)
* doc: create 2024 survey
1 parent e63bb87 commit 15d692b

File tree

1 file changed

+193
-0
lines changed

1 file changed

+193
-0
lines changed

‎surveys/2024-04/questions.md

Lines changed: 193 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,193 @@
1+
# Survey April 2024
2+
3+
## Demographics
4+
5+
- Where are you from? (countries list if possible - or open question)
6+
- Country
7+
8+
- How long have you been working with Node.js? (numbers list from 0 to 10+)
9+
10+
- In what kind of organizations are you working in?
11+
- big tech
12+
- company
13+
- startup
14+
- university
15+
- individual
16+
- other
17+
18+
- If working in a company, in which sector does your company operate? (single choice - Other should give an input)
19+
- Energy
20+
- Materials
21+
- Industrials
22+
- Health Care
23+
- Financials
24+
- Information Technology
25+
- Communication Services
26+
- Utilities
27+
- Real Estate
28+
- Other?
29+
30+
## Node.js Usage
31+
32+
- Which groups do you identify with? (multiple choice)
33+
- Direct end users: Users who run tools themselves
34+
- Application operators: Service and infrastructure providers
35+
- Application developers: Frontend tools consumers, backend server authors, tools authors
36+
- Library & package authors: Users who write libraries and packages to be included on other applications
37+
- Node.js core maintainers: Developers working directly on Node.js, individuals participating in Working Groups
38+
- Organization with investments in Node.js (eg: Enterprises, Gouvernement bodies, Startups, Non-profit, Education, Security)
39+
40+
- Are you part of a group not covered ? If yes which one ? (open question)
41+
42+
- What is your use cases of Node.js ? (multiple choice) (open question - Other should give an input)
43+
- Cli tools
44+
- Testing
45+
- Development of APIs with Microservices
46+
- Development of APIs with Serverless
47+
- Development of APIs with Other
48+
- Building static front end applications
49+
- Deploying front end applications (Next.js, Remix, etc...)
50+
- Script and automation (bots, scrapers)
51+
- Proxy
52+
- other
53+
54+
## What Node.js binaries do you use
55+
56+
- What is your Operating System for your local development environment ? (single choice - Other should give an input)
57+
- Linux
58+
- Windows
59+
- macOS
60+
- Linux with Docker
61+
- Windows with Docker
62+
- macOS with Docker
63+
- Windows with WSL
64+
- Other?
65+
66+
- What is your Operating System in which you are running Node.js in production ? (multiple choice - Other should give an input)
67+
- Linux/Unix
68+
- Windows
69+
- macOS
70+
- Linux with Docker
71+
- Windows with Docker
72+
- macOS with Docker
73+
- Other?
74+
75+
- What architecture is the machine you are running Node.js in production? (multiple choice - Other should give an input)
76+
- x64
77+
- x32
78+
- arm
79+
- ppc
80+
- s390
81+
- Don't know
82+
- Other?
83+
84+
- How do you get your `node` executables? (multiple choice – Other should give an input)
85+
- With a Node.js version manager: nvm, n, nave, nvs, volta, etc.
86+
- Using the official installer
87+
- Using package managers like npm or yarn and install Node.js as a package
88+
- Using a system package manager: apt-get, brew, dnf, yum …
89+
- Downloading binaries directly from Nodejs.org
90+
- Building Node.js from Source
91+
- Other
92+
93+
- What package manager do you use ? (multiple choice - Other should give an input)
94+
- npm
95+
- yarn v1
96+
- yarn modern (2+)
97+
- cnpm
98+
- pnpm
99+
- Other?
100+
101+
- Which version manager do you use (multiple choice - Other should give an input)
102+
- none
103+
- nvm
104+
- n
105+
- asdf
106+
- fnm
107+
- nodenv
108+
- nvs
109+
- volta
110+
- Other?
111+
112+
- How do you manage the package manager for your project? (multiple choice – Other should give an input)
113+
- I use one version installed globally for all my projects.
114+
- I use a tool to pick a specific version per project (e.g. Corepack, asdf, …).
115+
- I use containers.
116+
- Other?
117+
118+
## Project Priorities and Direction
119+
120+
- Which of the current [Technical Priorities](https://github.com/nodejs/node/blob/main/doc/contributing/technical-priorities.md) are important to you ? (multiple choice)
121+
- Modern HTTP
122+
- Suitable types for end-users
123+
- Documentation
124+
- WebAssembly
125+
- ESM
126+
- Support for features from the latest ECMAScript spec
127+
- Observability
128+
- Permissions/policies/security model
129+
- Better multithreaded support
130+
- Single Executable Applications
131+
- TypeScript Support
132+
133+
- Are there technical priorities that you believe are missing (open question)
134+
135+
- What is important to you ? (multiple choice)
136+
- Good understanding of the direction of the project
137+
- Ability to affect the direction of the project
138+
- Consumable APIs and docs
139+
- Predictable and stable releases
140+
- Innovation at a consumable pace
141+
- Easy Installation
142+
- Easy issue reporting, resolution and collaboration
143+
- Broad deployment platform support
144+
- Broad development platform support
145+
- Consistent and intuitive error handling
146+
- Runtime diagnostic tooling
147+
- Development time diagnostic tooling
148+
- Relevant APIs in core
149+
- Module/dependency info and management
150+
- Ways to fund their work
151+
- Reasonable resource usage/performance
152+
- Good security and CVE practices
153+
- Good CI infrastructure and experience in the project
154+
- Supportive Collaborators and Environment in the project
155+
- Better ways to build consensus in the project
156+
- Easy contribution workflow
157+
- Ability to embed and bundle the Node.js runtime
158+
- A well maintained and secure standard library
159+
- Assets that show Node.js is a good choice
160+
161+
- What is important to you that is not in this list? (open question)
162+
163+
## Technical Questions
164+
165+
- Regardless of how your code is written in its original form, when it runs in production, does it contain ES module syntax (`import`/`export`)?
166+
- Yes
167+
- No
168+
169+
- For those of you wishing to use ESM in an existing application, what have been the pain points or blockers preventing you from doing so (if any)? (open question)
170+
171+
- Are you using the following experimental features of Node.js (multiple choice)?
172+
- Corepack
173+
- Async Hooks
174+
- Permission model / Policies
175+
- Single Executable Application
176+
- Startup Snapshot
177+
- Loader hooks (`--loader` or `module.register()`)
178+
- Network import (`import 'http://...'`)
179+
- WASI
180+
- VM Modules (`--experimental-vm-modules`)
181+
- Watch mode (`--watch`)
182+
- WebSocket client
183+
- Trace events (`--trace-event-categories` or `node:trace_events`)
184+
- Dotenv (`--env-file`)
185+
- Import attributes
186+
187+
- Are you using the following new stable features (multiple choice):
188+
- Test runner (`node:test`)
189+
- Web Crypto (`globalThis.crypto` or `crypto.webcrypto`)
190+
- Web Streams (`node:stream/web`)
191+
- Fetch
192+
193+
- Do you encounter any recurring issues when using Node.js that you would like to share with us ? (open question)

0 commit comments

Comments
 (0)