Skip to content

Commit

Permalink
Clarify PoC
Browse files Browse the repository at this point in the history
We've run into issues before in CSSWG where someone has interpreted the priority of constituencies in an overly-absolute manner. This sentence captures our use of the term, which has served us well.
  • Loading branch information
tabatkins authored and robpalme committed Jun 3, 2024
1 parent f72de57 commit 059b864
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion terminology.md
Original file line number Diff line number Diff line change
Expand Up @@ -496,12 +496,14 @@ Some real-world examples:

The idea that when differing perspectives come into conflict, our decisions ought to prioritize them in the following (descending) order:

1. End users
1. End users (tool and website users)
2. JavaScript authors
3. JavaScript engine implementers
4. ECMAScript specification authors
5. Theoretical purity

This ordering is not absolute; a small cost or benefit to a higher-priority group can be overridden by a sufficiently large cost or benefit to a lower-priority group.

While this is not an explicitly adopted goal of TC39, it is a common standards concept which delegates often refer to.

### References
Expand Down

0 comments on commit 059b864

Please sign in to comment.