On Apr 18, 2011, at 12:24 AM, Garrett Smith wrote: > Implementations are motivated to get scripts working and conform to > specs. How could Ecma encourage developers to stop using ASI? I > initially thought that standard warnings in strict mode would help.
No. My earlier reply to your previous post pointed out how web content is unmaintained for stretches, or ages. Jason also pointed out that warnings nag the user, not the developer -- blaming the wrong party does not help and it can hurt. We had a "strict option" (SpiderMonkey's warning-enabling mode that predated ES5 strict by almost a decade) to warn about 'with' usage. We got only grief for it. We removed it (this is the only difference from our strict-warnings option and ES5 strict now, IIRC). On the web, besides not breaking the web, and not going out of business as a minority-share browser vendor by tilting at windmills, it is crucial to avoid blaming or nagging the user. /be _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
