On Wed, Dec 5, 2012 at 5:04 AM, Claus Reinke <[email protected]> wrote: > if you were browsing the spec trying to figure out what > super is about in JS, how much of the spec would you have to > read to answer that question, and how many readers succeed?
This is a very clear statement of the problem -- browsing the spec to figure out what X is about in JS is a bad idea. But that is as it should be. The spec formally defines the language; it is not for browsing to learn about the language. If you want to learn what a new feature like `super` does, you'll want to read blog posts and examples, until it appears in tutorials on the web, and then it will appear in future versions of Dave Herman's or David Flanagan's or Doug Crockford's books, if they decide to write them. If you ask the spec to serve two masters, then it will do one badly. In the Scheme community, the existence of a spec that many people find to be a good introduction to learning the language has been actively bad for the future development of the language. -- sam th [email protected] _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
