feat: update technical priorities for 2023 by sheplu · Pull Request #47523 · nodejs/node · GitHub

Update of the technical priorities from the last next-10 meeting during the Collaborator Summit (October 2022 in Dublin)

Review requested:

@nodejs/tsc

Suggested change

      
            ## ESM
          
            ## ES Modules (ESM)

I’m not sure what “primordial” means in this context.

Suggested change

      
            Small software footprints refer to software that has a minimal impact on system resources such as memory and processing power. This can be achieved through various methods such as optimizing code, reducing the number of dependencies, or using lightweight frameworks. Smaller footprints can lead to faster startup times, reduced memory usage, and improved overall system performance. This is primordial for Node.js to be a lightweigh proposition inside the ecosystem as it is used across a wild variety of projects, from web application to IoT and serverless.
          
            Small software footprints refer to software that has a minimal impact on system resources such as memory and processing power. This can be achieved through various methods such as optimizing code, reducing the number of dependencies, or using lightweight frameworks. Smaller footprints can lead to faster startup times, reduced memory usage, and improved overall system performance. This is fundamental for Node.js to be a lightweight proposition inside the ecosystem as it is used across a wild variety of projects, from web application to IoT and serverless.

+1 on using fundamental as the wording

Why do we need older versions below the current one? Can this file just represent the current priorities list, and the older versions are in the git history?

Suggested change

      
            Small software footprints refer to software that has a minimal impact on system resources such as memory and processing power. This can be achieved through various methods such as optimizing code, reducing the number of dependencies, or using lightweight frameworks. Smaller footprints can lead to faster startup times, reduced memory usage, and improved overall system performance. This is primordial for Node.js to be a lightweigh proposition inside the ecosystem as it is used across a wild variety of projects, from web application to IoT and serverless.
          
            Small software footprints refer to software that has a minimal impact on system resources such as memory and processing power. This can be achieved through various methods such as optimizing code, reducing the number of dependencies, or using lightweight frameworks. Smaller footprints can lead to faster startup times, reduced memory usage, and improved overall system performance. This is primordial for Node.js to be a lightweight proposition inside the ecosystem as it is used across a wild variety of projects, from web application to IoT and serverless.

I'd suggest we make the doc just contain the current version of the priorities. We can also track changes through GitHub history. That would also make reviewing what's changing easier.

I think we should leave this one in. Just because it was not in the current brainstorm does not mean it's still not important to the project.

I think we should leave this one in. Just because it was not in the current brainstorm does not mean it's still not important to the project. I believe this one will continue to be important almost forever :)

@sheplu it's still hard to see the differences between the current/new version as sections are moved around. Is that necessary or could it be updated so that sections stay in the same order. I don't think we implied any priority based on the order that they were listed in.

Ultimately most serverless runtimes are closed-source forks of Node.js, patched to support the needs of their cloud. Given that Serverless vendors are not keen to participate in the development of Node.js, nor do they provide public feedback, I don't see how this priority could be translated into actual work.

I'm +1 to support whoever shows up and wants to collaborate with the Node.js project. Supporting companies that are not willing to give back is not something I can endorse.

I think a goal could be to have those companies start collaborating on the project, but I don't think "serverless" could be a technical priority.

Suggested change

      
            Developer experience (DX) refers to the overall experience a developer has when working with a software development platform, framework, or tool. It encompasses all aspects of the developer's interactions with the system, from installation and configuration to writing code and debugging. A good DX prioritizes ease of use, efficiency, and productivity, and can lead to faster development times, higher quality code, and greater developer satisfaction. Factors that can impact DX include documentation, community support, testing tools, and integration with other systems.
          
            Developer experience (DX) refers to the overall experience a developer has when
          
            working with a software development platform, framework, or tool. It encompasses
          
            all aspects of the developer's interactions with the system, from installation
          
            and configuration to writing code and debugging. A good DX prioritizes ease of
          
            use, efficiency, and productivity, and can lead to faster development times,
          
            higher quality code, and greater developer satisfaction. Factors that can impact
          
            DX include documentation, community support, testing tools, and integration with
          
            other systems.

Suggested change

      
            _Present in: 2021_
          
            _Present in: 2021_

Suggested change

      
            _Present in: 2021_
          
            _Present in: 2021_

This one seemed to be mentioned quite a bit in the Community survey so may be worth leaving in.

@sheplu I don't think this comment was addressed. Can you take another look.

good catch !

All issues should be fixed
@mhdawson @GeoffreyBooth @aduh95 @mcollina

Suggested change

      
            of use,efficiency, and productivity, and can lead to faster development times,
          
            of use, efficiency, and productivity, and can lead to faster development times,

Suggested change

      
            been adopted asthe equivalent in the broader JavaScript ecosystem and
          
            been adopted as the equivalent in the broader JavaScript ecosystem and

@mcollina @aduh95 @mhdawson it should be fixed :)

Suggested change

      
            As TypeScript becomes usage continue to grow and the technology is more and 
          
            more prominent, improving its support is vital to provides a great developer 
          
            experience for newcomers or experienced users.
          
            As TypeScript usage continues to grow and gains more prominence in the
          
            ecosystem, enhancing its support is essential for delivering an improved
          
            developer experience for newcomers and experienced users alike.

done @aduh95

LGTM

Seeing as it’s not 2023 anymore, I think it’s time we landed this.

lgtm

PR-URL: #47523 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il>

Landed in 53aed88

PR-URL: #47523 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il>

nodejs-github-bot added the doc Issues and PRs related to the documentations. label Apr 12, 2023

GeoffreyBooth reviewed Apr 12, 2023

View reviewed changes

mscdex reviewed Apr 12, 2023

View reviewed changes

sheplu force-pushed the technical-priorities-2023 branch from b1cfce4 to 8c9f914 Compare May 24, 2023 13:52

mhdawson reviewed May 24, 2023

View reviewed changes

sheplu mentioned this pull request Jun 21, 2023

Review easy retros from Collab summit and do updates as appropriate nodejs/next-10#165

Closed

mcollina requested changes Jun 29, 2023

View reviewed changes

aduh95 reviewed Jun 29, 2023

View reviewed changes

sheplu force-pushed the technical-priorities-2023 branch from 8c9f914 to da5cbf5 Compare August 30, 2023 13:06

sheplu marked this pull request as ready for review August 30, 2023 14:21

mhdawson reviewed Aug 30, 2023

View reviewed changes

sheplu force-pushed the technical-priorities-2023 branch 4 times, most recently from 2d53b68 to da7ed50 Compare September 1, 2023 08:48

aduh95 reviewed Jan 24, 2024

View reviewed changes

mhdawson reviewed Jan 25, 2024

View reviewed changes

mcollina reviewed Jan 25, 2024

View reviewed changes

Comment thread doc/contributing/technical-priorities.md Outdated

sheplu force-pushed the technical-priorities-2023 branch from da7ed50 to 82129a4 Compare January 30, 2024 06:03

aduh95 reviewed Jan 30, 2024

View reviewed changes

mhdawson approved these changes Jan 31, 2024

View reviewed changes

sheplu force-pushed the technical-priorities-2023 branch from 82129a4 to b66df02 Compare February 5, 2024 06:45

doc: update technical priorities for 2023

f6d53b0

sheplu force-pushed the technical-priorities-2023 branch from b66df02 to f6d53b0 Compare February 5, 2024 07:04

aduh95 approved these changes Feb 5, 2024

View reviewed changes

mcollina approved these changes Feb 5, 2024

View reviewed changes

MoLow approved these changes Feb 5, 2024

View reviewed changes

mhdawson closed this Feb 15, 2024

marco-ippolito mentioned this pull request Mar 1, 2024

v21.7.0 proposal #51932

Merged

richardlau mentioned this pull request Mar 25, 2024

v20.12.0 proposal #52212

Merged

	of use,efficiency, and productivity, and can lead to faster development times,
	of use, efficiency, and productivity, and can lead to faster development times,

	been adopted asthe equivalent in the broader JavaScript ecosystem and
	been adopted as the equivalent in the broader JavaScript ecosystem and

feat: update technical priorities for 2023 by sheplu · Pull Request #47523 · nodejs/node · GitHub

Uh oh!

Uh oh!

feat: update technical priorities for 2023 - #47523

feat: update technical priorities for 2023#47523sheplu wants to merge 1 commit intonodejs:mainnodejs/node:mainfrom sheplu:technical-priorities-2023sheplu/node:technical-priorities-2023Copy head branch name to clipboard

Conversation

sheplu commented Apr 12, 2023

Uh oh!

nodejs-github-bot commented Apr 12, 2023

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mhdawson commented Apr 13, 2023

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mhdawson commented Jun 28, 2023

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

sheplu commented Jan 24, 2024

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mhdawson Jan 25, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

sheplu commented Jan 30, 2024

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mhdawson left a comment

Choose a reason for hiding this comment

Uh oh!

GeoffreyBooth commented Feb 1, 2024

Uh oh!

mcollina left a comment

Choose a reason for hiding this comment

Uh oh!

mhdawson commented Feb 15, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

feat: update technical priorities for 2023#47523
sheplu wants to merge 1 commit into
nodejs:mainfrom
sheplu:technical-priorities-2023

mhdawson Jan 25, 2024 •
edited
Loading