[4:01]<Dantman> I made a chunk of code that'll upgrade a ES engine that doesn't yet support parsing ISO dates to support 2000-01-01T00:00:00.000Z at the least (just a fully expanded UTC string with or without milliseconds). [4:02]<Dantman> I haven't completed it (it's missing the shorter forms, and timezones) but it's all I need for now. [4:03]<Dantman> Anyone want me to put it in a gist so they can expand it? I'll put the result in Wrench.js under MIT. [4:03]<Dantman> Then anyone with a CommonJS engine that only has ES3 so far can add ES5's handling of ISO dates to it. [4:04]<Dantman> (I believe that would fall under the category of ES5 features that can be implemented in ES3 that we agreed all compliant engines should support) [4:09]<Dantman> Meh, I'll actually just post the gist to the list. [4:57]<Dantman> T_T Something is wrong with my booleans [17:04]<ondras> http://net.tutsplus.com/tutorials/javascript-ajax/top-10-things-that-javascript-got-wrong/ [17:06]<ashb> 'If null is the absence of a value' not really [17:06]<ashb> that would be undefined [17:06]<ashb> 3. welcome to how IEE745 says it should behave [17:07]<ashb> 5. if you are sniffing UA strings you are doing it wrong [17:09]<ashb> 7. w.t.f. "Consider the first item, &; it would be much more efficient to use the && operator, as it's quicker" [17:09]<ashb> wtf is he on about there [17:10]<ashb> 9. again, welcome ti iee745 [17:17]<ondras> exactly. [17:56]<Wes-> The author of that page is ... not overly proficient IMHO [17:57]<Wes-> The only thing he really gets right is 10, and his conclusion is incorrect [17:57]<ashb> Wes-: 6. is an annoyance too [17:58]<Wes-> ashb: JS scoping rules may be annoying, but they are hardly inconsistent [17:58]<ashb> true [17:59]<Wes-> well, except for let vs. var but that's a whole other story