David Bruant wrote:
the other is new built-in functions (for Array, Math, Object, etc.).
Maybe the latter category could be "(partially) delegated" to the
developer community and ratified by TC39.
I constantly endorse this, averring that TC39 will screw up any library
design exercise of necessary scale, like NPM's most popular, or smaller
gems such as underscore.
The way to get these right is github.com, not Ecma TC39!
I foresee that with modules, a new field for this second category is
opening and there will have some important discussion about what
module should be in the standard and which shouldn't. Maybe the
responsibility for this part could be also shared with the developer
community since they are those who usually write these functions (out
of need).
It's shared only in the sense that TC39 writes down de-jure specs that
browser vendors and others treat as normative. We have to do right, and
spec stuff people want. By spec'ing what people actually use, based
mostly on the cream that we skim off of github, we avoid all the risks
of trying to design API sets in too narrow a setting.
Your point about overlap, no dichotomies, is good too. We need
cross-training among developers and TC39ers where feasible. TC39ers I
know are all writing more JS over time. I'm trying to kick the C++ habit
myself ;-).
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
