Re: Top 10 things I learned my 1st month as a Monk

Replies are listed 'Best First'.
Re^2: Top 10 things I learned my 1st month as a Monk by BrowserUk (Patriarch) on Jul 22, 2007 at 13:20 UTC
I've no argument with your choice--it is definitely yours alone to make--but why would you not use strict? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^2: Top 10 things I learned my 1st month as a Monk by Argel (Prior) on Jul 23, 2007 at 17:33 UTC
Is there some performance gain to not using strict? Otherwiese, even if you normally do everything in a strictly correct manner wouldn't it still make sense to use strict just in case you slip-up?	[reply]
Re^3: Top 10 things I learned my 1st month as a Monk by mr_mischief (Monsignor) on Jul 23, 2007 at 18:55 UTC
Some of the strict checks are runtime checks. However, the overhead involved probably won't be noticed. If your program is so time-critical that strict pushes it past some limit, there's likely much better ways to get that time back. Removing strictness for performance seems like a very premature optimization.	[reply]
Re^2: Top 10 things I learned my 1st month as a Monk by girarde (Hermit) on Jul 25, 2007 at 16:22 UTC
In that case you are probably not doing anything really new. `use strict` helps avoid surprises.	[reply] [d/l]