 |
From: Marcel Laverdet <mar...@laverdet.com>
Date: Sun, 22 Jan 2012 02:46:21 -0600
Local: Sun, Jan 22 2012 3:46 am
Subject: Re: [nodejs] should issue a warning when "strict mode"; is missing
> +1 to adding "use strict" to the module wrapper, so that all server side code is implicitly strict, whether it says so or not. Having uses of octal be a bit more awkward is a small price to pay for the increase in sanity. Bit surprised to hear this from you! It seems dangerous to introduce this.. @isaac > Marcel, you know full well that responsible semicolon minimalists would balk at the very notion of starting a line with ( and not prefixing it with a semicolon. > This "always" "never" business is a strawman duel. No one who knows what Dude I wasn't trying to turn this into a duel. I'm saying that neither @ryan > I always use semicolons where they belong, or at least, that is my intention. In what way is this not safe? For the most part you should be fine. The only thing I could realistically } foo() returns undefined! On Fri, Jan 20, 2012 at 2:20 PM, Mark Miller <erig...@gmail.com> wrote:
> Hi Isaac, because of this octal impediment, we've decided to support 0o666 > octal literals, and 0b10101 binary literals while we're at it, to ES6. > However, in the meantime, I think this is a truly terrible reason to burden > the community with the continued presence of non-strict server-side code. > Think of non-strict code as toxic waste -- we can't deny its inevitable > continued existence, but let's please keep it out of places where people > are still living (active code being actively maintained). It isn't even > lexically scoped. Going forward, its only remaining purpose should be to > keep old websites working even when their sources are no longer being > actively maintained, i.e., most of the web, but essentially none of NodeJS > or other server-side code. > +1 to adding "use strict" to the module wrapper, so that all server side > On Fri, Jan 20, 2012 at 11:27 AM, Isaac Schlueter <i...@izs.me> wrote: >> A while ago (0.5, I think?) I looked into adding a NODE_USE_STRICT >> It didn't seem to affect any of our benchmarks. So, to claim speed >> Attributing 99% of non-strict JS use to laziness is a bit >> On Fri, Jan 20, 2012 at 11:11, AJ ONeal <coola...@gmail.com> wrote: >> > 99% Laziness (the inefficient kind) >> > Since node is all about speed and "use strict"; mode allows for >> > I'm watching one of the Crockford videos right now as and just aching >> > AJ ONeal >> > -- >> -- > -- > Cheers, > -- You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||