feat: update technical priorities for 2023 #47523

sheplu · 2023-04-12T14:23:38Z

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

nodejs-github-bot · 2023-04-12T14:23:43Z

Review requested:

@nodejs/tsc

GeoffreyBooth · 2023-04-12T16:44:32Z

doc/contributing/technical-priorities.md

+
+Version from the [mini-summit](https://github.com/nodejs/next-10/issues/1) on October 1st 2022.
+
+## ESM


Suggested change

## ESM

## ES Modules (ESM)

GeoffreyBooth · 2023-04-12T16:46:13Z

doc/contributing/technical-priorities.md

+
+## Small footprint
+
+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.


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

GeoffreyBooth · 2023-04-12T16:50:25Z

doc/contributing/technical-priorities.md

+
+------
+
+Version from the [mini-summit](https://github.com/nodejs/next-10/issues/76) on August 5th 2021.


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?

mscdex · 2023-04-12T18:53:04Z

doc/contributing/technical-priorities.md

+
+## Small footprint
+
+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.


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.

mhdawson · 2023-04-13T13:26:52Z

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.

mhdawson · 2023-05-24T16:51:52Z

doc/contributing/technical-priorities.md

-must provide good support for using multiple threads
-to ensure the continued growth and success of Node.js.
-
-## Single Executable Applications


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.

mhdawson · 2023-05-24T16:52:35Z

doc/contributing/technical-priorities.md

-develop and improve its ESM implementation to stay relevant and ensure
-continued growth for the next 10 years.
-
-## Support for features from the latest ECMAScript spec


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 :)

mhdawson · 2023-06-28T21:52:00Z

@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.

mcollina · 2023-06-29T08:02:17Z

doc/contributing/technical-priorities.md


-## WebAssembly
+Serverless is a cloud computing model where the cloud provider manages the underlying infrastructure and automatically allocates resources as needed. Developers only need to focus on writing code for specific functions, which are executed as individual units of work in response to events. Node.js is one of the main technology used by developers in this field therefore it is crucial for us to provide a great solution.


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.

aduh95 · 2023-06-29T08:41:13Z

doc/contributing/technical-priorities.md

+
+## Developers-first DX
+
+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

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.

aduh95 · 2023-06-29T08:41:19Z

doc/contributing/technical-priorities.md

-for using Node.js in these situations. This is important to support
-the expansion of where/when Node.js is used in building solutions.
+## Modern HTTP 
+_Present in: 2021_


Suggested change

_Present in: 2021_

_Present in: 2021_

doc/contributing/technical-priorities.md

aduh95 · 2023-06-29T08:41:33Z

doc/contributing/technical-priorities.md

+of the solution. This includes implementations of “host” APIs like WASI.
+
+## Documentation
+_Present in: 2021_


Suggested change

_Present in: 2021_

_Present in: 2021_

doc/contributing/technical-priorities.md

mhdawson · 2023-08-30T14:21:43Z

doc/contributing/technical-priorities.md

-not result in 100% protection as this will still help organizations
-manage their overall risk level.
-
-## Better multithreaded support


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 !

sheplu · 2024-01-24T14:49:55Z

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

aduh95 · 2024-01-24T14:53:04Z

doc/contributing/technical-priorities.md

+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,


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,

mhdawson · 2024-01-25T20:42:54Z

doc/contributing/technical-priorities.md

+
+The CommonJS module system was one of the key components that led to the
+success of Node.js in its first 10 years. ESM is the standard that has
+been adopted asthe equivalent in the broader JavaScript ecosystem and


Suggested change

been adopted asthe equivalent in the broader JavaScript ecosystem and

been adopted as the equivalent in the broader JavaScript ecosystem and

doc/contributing/technical-priorities.md

sheplu · 2024-01-30T06:05:52Z

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

aduh95 · 2024-01-30T08:51:29Z

doc/contributing/technical-priorities.md

+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.


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

mhdawson

LGTM

GeoffreyBooth · 2024-02-01T00:15:57Z

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

mcollina

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>

mhdawson · 2024-02-15T22:08:57Z

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>

PR-URL: nodejs#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>

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

doc/contributing/technical-priorities.md Show resolved Hide resolved

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: update technical priorities for 2023 #47523

feat: update technical priorities for 2023 #47523

sheplu commented Apr 12, 2023

nodejs-github-bot commented Apr 12, 2023

GeoffreyBooth Apr 12, 2023

GeoffreyBooth Apr 12, 2023

mhdawson May 24, 2023

GeoffreyBooth Apr 12, 2023

mscdex Apr 12, 2023

mhdawson commented Apr 13, 2023

mhdawson May 24, 2023

mhdawson May 24, 2023

mhdawson commented Jun 28, 2023

mcollina Jun 29, 2023

aduh95 Jun 29, 2023

aduh95 Jun 29, 2023

aduh95 Jun 29, 2023

mhdawson Aug 30, 2023

mhdawson Jan 25, 2024

sheplu Jan 30, 2024

sheplu commented Jan 24, 2024

aduh95 Jan 24, 2024

mhdawson Jan 25, 2024 •

edited

Loading

sheplu commented Jan 30, 2024

aduh95 Jan 30, 2024

sheplu Feb 5, 2024

mhdawson left a comment

GeoffreyBooth commented Feb 1, 2024

mcollina left a comment

mhdawson commented Feb 15, 2024


		Version from the [mini-summit](https://github.com/nodejs/next-10/issues/1) on October 1st 2022.

		## ESM


		## Small footprint

		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.


		------

		Version from the [mini-summit](https://github.com/nodejs/next-10/issues/76) on August 5th 2021.


		## WebAssembly
		Serverless is a cloud computing model where the cloud provider manages the underlying infrastructure and automatically allocates resources as needed. Developers only need to focus on writing code for specific functions, which are executed as individual units of work in response to events. Node.js is one of the main technology used by developers in this field therefore it is crucial for us to provide a great solution.


		## Developers-first DX

		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.

	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 #47523

feat: update technical priorities for 2023 #47523

Conversation

sheplu commented Apr 12, 2023

nodejs-github-bot commented Apr 12, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mhdawson commented Apr 13, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mhdawson commented Jun 28, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sheplu commented Jan 24, 2024

Choose a reason for hiding this comment

mhdawson Jan 25, 2024 • edited Loading

Choose a reason for hiding this comment

sheplu commented Jan 30, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mhdawson left a comment

Choose a reason for hiding this comment

GeoffreyBooth commented Feb 1, 2024

mcollina left a comment

Choose a reason for hiding this comment

mhdawson commented Feb 15, 2024

mhdawson Jan 25, 2024 •

edited

Loading