Comments on: When JavaScript makes no sense

By: Nathan L Smith

Nathan L Smith — Wed, 28 Jul 2010 16:40:40 +0000

wtfjs.com’s content is generated from a Git repo conveniently available here: http://github.com/brianleroux/wtfjs

I think they’re using Heroku’s beta Node.js support, and I also think Heroku just updated to a newer version of Node, which may have broken the site. That’s just speculation, though.

By: Thomas Fuchs

Thomas Fuchs — Wed, 28 Jul 2010 14:10:23 +0000

@Pietro Seeing the heroku error here too, now. Hope I haven’t miraculous’ed the site…

By: Pietro

Pietro — Wed, 28 Jul 2010 14:03:54 +0000

http://wtfjs.com/ returns an Heroku error here…
About your javascript findings, yes there are some fun stuffs. These and some more can be found in the “Crockford On JavaScript” videos in the Yahoo YUI Theater: http://developer.yahoo.com/yui/theater/

For example:
9007199254740992 === 9007199254740992+1

By: Mathias Bynens

Mathias Bynens — Wed, 28 Jul 2010 13:33:23 +0000

Thankfully, ECMAScript 5 gets rid of octal literals, meaning parseInt("08") is now simply 8 (not only in strict mode!).

By: Thomas Fuchs

Thomas Fuchs — Wed, 28 Jul 2010 13:24:29 +0000

@Boyan http://wtfjs.com/ works fine here. Maybe your provider? If you use Chrome, try an other browser (I had DNS issues with Chrome in the past).

By: Boyan Yurukov

Boyan Yurukov — Wed, 28 Jul 2010 13:21:48 +0000

wtfjs seems to be down