Dr J R Stockton said:
For example, all references to 1970 need to include a UTC, and
"midnight" should not be used. "UTC 1970.0" is exact, and I don't
see how anyone intelligent enough to program successfully can fail
to understand it. Or "1970-01-01 00:00:00 UTC".
Method getFullYear does not return a 4-digit year - try
new Date(-5e13).getFullYear() and new Date(5e15).getFullYear() - it
returns a Number.
Interesting. The updated page will certainly benefit from these hints.
The worldclock page is best deleted, as a precaution against anyone
believing it.
Anyone blindly believing anything only deserves so, especially on the www.
People go online for information, not for knowledge. The page may be full of
inaccuracies, it may be one big lie (as was the page that I originally
copied), but it can satisfy much curiosity, ignite even more, and it may
spark a thought in one visitor about the wonders of our world. In that I
find satisfaction, until of course you convince me of some real evil in the
page.
Probably me; I was in fact trying to find out who was responsible for
the site. One should never pay much attention to technical documents
that do not declare their authorship and give some indication of age.
My picture of you has always been someone in his fifties, I cannot say why,
I don't remember such indication being prominently advertised on your site,
I must say. And if I told you I happen to turn 36 today, and gave you an url
such as
http://www.vansandick.com/familie/kalender/?20070330 to make it look
convincing, wouldn't that be reason enough to be suspicious? Then why should
credibility of any text depend on the name under it? What matters is what
works. Especially technical texts are easy to judge by empirically trying
out the claims that are made. Experiment is key. That 's how information
becomes knowledge. Any text that shows me something I haven't tested yet, is
worthwhile, and I find that the older I get, more and more of such texts are
written by nameless youths.
That site has no real authority; and the argument in #with is not
entirely convincing when carefully examined.
I 'm not building on their authority, just gave a pointer. The argument
could be expressed stronger, shall we say "The problem is that the
programmer has no way to verify that input1 or input2 are actually being
resolved as properties of the form elements array" is a bit long and
winding, but it stands solid. I don't think there are words that will
entirely convince you. Inside the 'with' block, there is no way to tell an
independent input2 from a 'with'ed input2. There is a ghost host object at
every level in the scope chain. Ay, there 's the rub. There is no defense
against the ambiguity created with 'with'. I also refer to a contemporary
thread started by Rasmus Kromann-Larsen, 'Eliminating "with"...', especially
the very first paragraph: "I'm currently writing a master thesis on static
analysis of JavaScript, and after investigating the with statement, it only
[became] even more evident to me that the with statement is indeed bad." See
for the arguments:
http://groups.google.nl/group/comp....read/thread/a953bd621436d8d3/f877b6f155fd916a
If "with" is used wantonly and there are errors in the code, it can
indeed be difficult to see what is happening.
Like you say.
But when there is no global date object, and the "with" clearly
uses a Date Object, and the identifiers in the statement are not
going to have other meanings, using it can add no problems.
With all conditions met, I probably am with you on the Date object argument,
but I maintain that continuing to use 'with' sustains a flaw in the
language. We 're really better off without.