> Hope this is clear. To your point, and as Francois posted, teaching people to > leave out 'new' is not going to work in various cases. Better to teach > subsets starting with ES5 strict or smaller, and build up from there > (including XHR at some point). A fair amount (not all) of ES6 should be "more > advanced", not "beginner". > > In general, trying to teach new stuff that's optional-by-design (remember, > 1JS) as if it were usable exclusive of old stuff looks like a mistake to me. > > If there's a great ES6->ES5 transpiler (traceur is shaping up nicely, thanks > Arv) then perhaps. That is still in the future, in part because ES6 is not > done yet, nor is traceur -- and nor is experience with such a "JS pedagogy" > built on a future-subset-first teaching approach.
Right. Initially, I’d teach ES5 and a “what’s new in ES6”. Later, I would initially omit some ES5 things, e.g.: Start with `let` and explain `var` and IIFEs much later. Instead of subsetting, I prefer “simple (possibly even simplistic) rules” for beginners. For example, they can afford to initially ignore ASI and always use semicolons. And they can afford to initially ignore == and always use ===. I use such rules for myself, too. It allows me to stay sane w.r.t. to some of the details. -- Dr. Axel Rauschmayer [email protected] home: rauschma.de twitter: twitter.com/rauschma blog: 2ality.com
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
