excluding features from sloppy mode

Brandon Benvie brandon at brandonbenvie.com
Sat Dec 29 17:03:09 PST 2012

Put everything new in ES6 as implicit opt-in for strict mode? It certainly
is the simplest of all options, both for implementors and users. It also
removes the "big enough carrot" problem. Any individual feature may not be
enough of a carrot to sway a user, and taken as one by one choice, might
leave room for devs to pick and choose around strict mode (if there ends up
being some perceived difficulty or annoyance factor). But I can't imagine
anyone opting out of everything ES6 provides just to avoid strict mode. The
only reason people are likely to avoid everything in ES6 is compat concerns
which is orthaganol to strict mode.

Or something like require all ES6 features be inside modules, which
accomplishes the same thing. I know I saw this discussion before, or
something like it, but wasn't able to locate it.

On Saturday, December 29, 2012, Kevin Smith wrote:

> I gotta say, I'm in agreement with Mark (and even Andreas) here.  1JS,
> under all modes just isn't going to work (let[x] = y proves that).  And
> keeping track of what's allowed under which mode (and why) could get
> complicated and difficult to explain.
> But what about this?
>  One JS,
>  Under strict mode,
>  With awesome for all?
> Sounds good to me!
> { Kevin }
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20121229/fcd8d4e4/attachment.html>

More information about the es-discuss mailing list