On Mar 25, 2012, at 3:54 AM, Axel Rauschmayer wrote: > Now that the memories are still fresh – would it make sense to record how > some of the design decisions were arrived at? I’d expect that to help with > future feature additions and with reducing the amount of questions being > asked on es-discuss. Examples: What names of the <| operator have been > rejected and why? Why don’t class declarations have feature X? Etc.
FWIW, I record *huge* amounts of this kind of information in my private notes. It's not private out of any desire for secrecy, but simply because I try to get everything down as soon as I can, before my pitiful brain forgets it all, and as a result it's generally a mess of chicken scratch. Making it fit for consumption would take a lot of work. > To be sure that would be yet more work (which should be done by the proposal > authors, I guess), so I’m not sure it’s worth it, but it would be a great > resource for educating the masses. I hope to do this as much as possible, but it's the kind of thing that makes more sense to do when the dust settles, at least in any given area. Otherwise you end up wasting time polishing things that are about to change anyway. And as we go along I do try to state publicly any important rationale that needs to be explained in order to justify the decisions made. But design at the scale of a language covers an unimaginably huge space of alternatives, so it's just not always feasible to capture all the micro- and macro-decisions in real time and in a polished form. Dave _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
