Click here to Skip to main content
15,867,771 members

Comments by egozi13 (Top 7 by date)

egozi13 10-Mar-11 15:31pm View    
Deleted
Reason for my vote of 3
Although very accurate, this is not a tip, but a ripoff from the ECMAscript standard doc. It does not serve as a tip as it is difficult to understand and follow, and also copying from another place without a reference is not polite imo
egozi13 10-Mar-11 15:30pm View    
Deleted
Reason for my vote of 4
it is a good tip, and important for people to know this. but the explanation is not intuitive enough imo
egozi13 10-Mar-11 15:28pm View    
Deleted
dude - are you for real?
I clearly stated this in the tip - it is *not* a precise algorithm, and it is *not* meant to be accurate - but rather to give a javascript developer a quick understanding of "what is going on" without needing to delve into a long, boring spec document.

so - we have three alternations here:
1. your original one - neither accurate, nor useful for developers
2. mine - not accurate, but helpful, and points to the spec
3. Øyvind - accurate, but somewhat too long and detailed to be considered a helpful tip.

yours is definitely the worst, and you vote mine as 1? you have got to be kidding
egozi13 10-Mar-11 7:15am View    
Deleted
Allright guys. I've updated my tip to state clearly that it is not the precise algorithm, but a good and useful approximation (what I call a tip)
egozi13 9-Mar-11 13:48pm View    
Deleted
Copying from the ECMAscript standard is hardly a "tip". If anything it would have been better to link to there, or at least say where the data was copied from.

So, although my simplification is not accurate, it does serve to explain what is going on. I will revise the text though to state that.

BTW, the spec still does not explain why my example will alert "true".