search

nodejs / next-10

Repository for discussion on strategic directions for next 10 years of Node.js
Other
480 stars 24 forks source link

feat: add 2022 survey questions #173

Closed sheplu closed 1 year ago

sheplu commented 1 year ago

A draft of the questions we should be asking in our survey.

Some questions are the same as last year, others are new and a few are curated based on last year result.

Of the part What is important for you ? (Multiple choices) I used some of the choices from last year (especially the ones big the most answers) and added a few based on our cards from the Dublin Collaborator Summit

sheplu commented 1 year ago

@nodejs/next-10 To review for the next meeting #152

mcollina commented 1 year ago

I would add those two questions related to ESM:

  1. are you using native ESM, e.g. "type": "module" or .mjs, in your Node.js Development?
  2. are you planning to convert your application to native ESM?

cc @GeoffreyBooth

sheplu commented 1 year ago

Just added the two questions. With all the discussion we had but also people talking about that externally this seems to be an issue and having data would help us.

Thanks @mcollina

GeoffreyBooth commented 1 year ago

I would add those two questions related to ESM:

What are you hoping to learn from these questions?

I asked similar questions at the June summit and very few people were planning on converting existing applications to ESM but what seemed like every single hand in the room went up (about 50 people) when asked if they would start their next project in ESM. We could add a third question like “Are you planning to use native ESM for your next Node.js project?” or just replace the second question with this. But either way, what are we trying to learn? That ESM adoption is low?

I would be more interested in the follow up, like “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)?” and “For those of you trying to use ESM in a new application, what have been the pain points or blockers preventing you from doing so (if any)?” Questions like these would give us useful information in that we would know what issues need addressing for ESM usability.

sheplu commented 1 year ago

I can see to have a unique question for both next project and migration (as this is really linked)

Adding a question about the blocker points can be interesting but I am also pretty sure we already know the feedbacks, we mostly all have the same (I think - but can be useful to focus the efforts on the more vocals ones first). What do you think @GeoffreyBooth ?

GeoffreyBooth commented 1 year ago

I am also pretty sure we already know the feedbacks, we mostly all have the same

Do we? We knew the blockers 2-3 years ago, but hopefully most of those have been resolved by now. I know that lots of people are waiting for the Loaders API to go stable (which should happen soon) but I’m unaware of any other issues.

sheplu commented 1 year ago

Let's add it then :) ESM/CJS was a big discussion in Austin and we talked again about it during the Dublin collab summit so let's see what is the new feedback from the community !

joyeecheung commented 1 year ago

It would be valuable to have some data of architecture/OS that people are using to run Node.js and how long do they plan to use it too, to help decide when we are looking into dropping support of a certain platform.

sheplu commented 1 year ago

Everything updated following suggestions

mhdawson commented 1 year ago

I'm going to land this and we can PR in any follow on suggestions.