Build web apps in Javascript - new service open for beta

[Thomas 'PointedEars' Lahn]

[...] Thomas 'PointedEars' Lahn [...] wrote:
Peter Michaux wrote:
[...] Thomas 'PointedEars' Lahn [...] wrote:
David Mark wrote:
David Mark said the following on 2/21/2008 4:31 AM:
David Mark said the following on 2/21/2008 3:00 AM:
<snip>
will take a bit more research on the best way to do it.
Not really.
window.onload = myfunction;
Don't let Thomas know that
Proprietary and error-prone approach. I know.
Only in Thomas' warped mind is it.
Agreed.
Once you recognized that there is inherent truth in the statement that your
favorite (collection of) browser(s) is not the standard for every user agent
out there, you will see how mistaken you really are here.
Please explain.
There really is not much to explain. Assuming a proprietary feature to be
universally available is a jump to conclusions; a common fallacy, though.
Oh for the love of God. How many times are you going to dump on
window.onload without naming a single case where it might be
considered harmful?

As many times as I want to without running the risk of losing credibility

Too late. [...]

From what you replied it is now obvious that you clearly don't belong to the
aforementioned group, so your humble opinion about this does not matter at all.

Have a nice day.


PointedEars

 

[toby.oconnell]

Just him. It was his team that did the leg work and it saved them. The
only thing that saved me was my daily backups. Most of Monday was spent
double checking and making sure that everything from Wednesday, Thursday
and Friday got updated in the databases. They went to a paper back up
system and we had to make sure everything got entered and saved. It did
make me go to a complete daily backup. We were doing weekly backups on
the entire system and daily backups on critical data. Now, it is done
daily on the entire system.

They all know, without a doubt, how pissed off I can get though.

I'm a little late to this thread, but was wondering: Are you not using
a source code repository? If so, I don't understand why you would
need backups to save you (aside from cases where the repository gets
wiped). That would make the code much easier to roll back. It can
still be pretty mucked up if some "good" changes were mixed in with
the bad changes, though. Just curious because I would feel safer
reverting to a particular fine-grained, revision-based state than a
certain time-based state (of the backup).