Prioritizing Technical Values

[mhdawson]

Context from discussion:

This is around technical values, other values are important but not covered here. Make sure to clarify that up front.

Values from the brainstorm:

• Approachability (both technical and community)
• Stability
• User experience
• Developer experience
• Community
• Security
• Backwards compatibility(?)
• Performance
• Diagnostics
• Maintainability
• Web API compatibility
• Ecosystem (from FunRetro)
• Collaborator Velocity
• Great Documentation
• Adoption of new technologies
• Simplicity over complexity
• Planning for today versus all possible future options, Avoid needless complexity
• Tight focus/minimal surface
• LTS support for users still using older versions of Node
• Clear expectations set around support?
• Suitability for cloud/deployments?
• Suitability for IoT (e.g. low memory footprint)?

The goal is to expand this list to make it complete and to come up with some sort of prioritization that would be used in cases where they all cannot be satisfied.

An example might be Security over Performance or vice versa. We were not clear on what that might look like and how to arrange but this issue is to discuss see what progress we can make on that front.

[mhdawson]

Tagging for agenda as we plan to dive into this in the next meeting.

[mhdawson]

PR open nodejs/node#35145

[mhdawson]

Initial version of PR landed, closing