feat: update technical priorities for 2023

Author: sheplu

doc/contributing/technical-priorities.md

@@ -14,7 +14,12 @@ on August 5th 2021.
 They will be updated regularly and will be reviewed by the next-10 team
 and the TSC on a 6-month basis.
 
-## Modern HTTP
+
+Version from the [mini-summit](https://github.com/nodejs/next-10/issues/1) on October 1st 2022.
+
+## Modern HTTP 
+
+_Present in: 2021_
 
 Base HTTP support is a key component of modern cloud-native applications
 and built-in support was part of what made Node.js a success in the first
@@ -26,6 +31,8 @@ implementations of different versions concurrently.
 
 ## Suitable types for end-users
 
+_Present in: 2021_
+
 Using typings with JavaScript can allow a richer experience when using Visual
 Studio Code (or any other IDEs) environments, more complete documentation
 of APIs and the ability to identify and resolve errors earlier in the
@@ -37,6 +44,8 @@ to ensure there are good typings available for the public Node.js APIs.
 
 ## Documentation
 
+_Present in: 2021_
+
 The current documentation is great for experienced developers or people
 who are aware of what they are looking for. On the other hand, for
 beginners this documentation can be quite hard to read and finding the
@@ -47,14 +56,19 @@ path for newcomers.
 
 ## WebAssembly
 
+_Present in: 2021_
+
 The use of WebAssembly has been growing over the last few years.
 To ensure Node.js continues to be part of solutions where a
 subset of the solution needs the performance that WebAssembly can
 deliver, Node.js must provide good support for running
 WebAssembly components along with the JavaScript that makes up the rest
 of the solution. This includes implementations of “host” APIs like WASI.
 
-## ESM
+
+## ES Modules (ESM)
+
+_Present in: 2021_
 
 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 as
@@ -71,6 +85,8 @@ of choice and to ensure its continued growth for the next 10 years.
 
 ## Observability
 
+_Present in: 2021_
+
 The ability to investigate and resolve problems that occur in applications
 running in production is crucial for organizations. Tools that allow
 people to observe the current and past operation of the application are
@@ -84,34 +100,6 @@ applications on top of the runtime. In addition, it is also important to clearly
 document the use cases, problem determination methods and best
 practices for those tools.
 
-## Permissions/policies/security model
-
-Organizations will only choose technologies that allow them to sufficiently
-manage risk in their production deployments. For Node.js to
-continue its growth in product/enterprise deployments we need to ensure
-that we help them manage that risk. We must have a well-documented
-security model so that consumers understand what threats are/are
-not addressed by the Node.js runtime. We also need to provide
-functions/features which help them limit attack surfaces even if it does
-not result in 100% protection as this will still help organizations
-manage their overall risk level.
-
-## Better multithreaded support
-
-Today's servers support multiple threads of concurrent execution.
-Node.js deployments must be able to make full and efficient
-use of the available resources. The right answer is often to use
-technologies like containers to run multiple single threaded Node.js
-instances on the same server. However, there are important use cases
-where a single Node.js instance needs to make use of multiple threads
-to achieve a performant and efficient implementation. In addition,
-even when a Node.js instance only needs to consume a single thread to
-complete its work there can be issues. If that work is long running,
-blocking the event loop will interfere with other supporting work like
-metrics gathering and health checks. Node.js
-must provide good support for using multiple threads
-to ensure the continued growth and success of Node.js.
-
 ## Single Executable Applications
 
 Node.js often loses out to other runtimes/languages in cases where
@@ -121,3 +109,31 @@ components/approaches for doing this, they need to be better
 documented and evangelized so that this is not seen as a barrier
 for using Node.js in these situations. This is important to support
 the expansion of where/when Node.js is used in building solutions.
+
+## Serverless
+
+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.
+
+## 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 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.
+
+## 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.