JavaScript (aka Marlboro Country)

9:23 PM

Sometimes JavaScript land just feels like Marlboro Country. The sales pitch certainly feels similar:

Come to the hottest part of the United States. It's popular. It's everywhere. It's the future. Now: cover yourself in leather. Don't ask why. It's part of the feature set. Next: the temperature is 120 degrees, and you need to start a fire. It's not supposed to make sense, that's the point. You'll need to do this at noon every day. After about 10 days, you'll find yourself assaulting anyone _not_ starting noonday fires.

C'mon?! What's the worst that could happen?

Imagine: right now, you could be riding across a brush fire.. or maybe it's a dust storm.. or maybe.. who knows? Everything's mutable! Ride across anything you want. Of course, you are limited to desert colors (obviously).

Lest you be confused, I love JavaScript. While the language as specified is littered with nightmarish design flaws and obstacles reminiscent of trench warfare and carpet bombing (let's call them WATs), JavaScript's Good Parts are so good you might be forgiven for forgetting about that elephant in the bathroom (aka IE). Yet.

Yet and yet, the WATs do also rise. And they rise.

A few weeks ago, I began to set ink to digital paper to record the recipe for my new found WAT. There is a delightful tool for recording code demonstrations, The Code Player. While the demos presented are quite nice, I lost all 5 of my first drafts to bugs in the system. Still, you should keep an eye on it. I considered reverting to my old faithful, JSFiddle, which is fantastic for mocking up and testing code but less suited for driving a walk through. In the end, syntax highlighting in the blog will have to must suffice.

The municipal "we" begin with a simple function:

function doVerbOnNoun(aThing) {;

//In theory, if(aThing) should be equivalent to if(true == aThing)
if(aThing) {
console.log('Verbing on ' + aThing);
} else {
console.log('Not verbing on ' + aThing);

A naïve developer, like myself, would assume that our guarding if(truthy) would apply the loose, truthy type coercions we have been trained to avoid; and an undisciplined tester, like myself from a few moments ago, might almost be forgiven for missing the lawn for the dandelion. The following assertions execute as expected naïvely:

doVerbOnNoun('aThing'); //We verbed
doVerbOnNoun(''); //Verb, we did not

doVerbOnNoun(5); //We verbed
doVerbOnNoun(NaN); //Verb, we did not

doVerbOnNoun(true); //We verbed
doVerbOnNoun(false); //Verb, we did not

//Null and undefined:
doVerbOnNoun(null); //Verb, we did not
doVerbOnNoun(undefined); //Verb, we did not

But if the republic of we would but pause and stare but briefly into the abyss, it becomes immediately apparent that loose, truthy typely coerced evaluation is not happening here.

doVerbOnNoun('a string of some sort'); //We verbed
console.assert(true == 'a string of some sort', "'true' != 'a string of some sort'"); //Assertion fails

doVerbOnNoun(5); //We verbed
console.assert(true == 5, "'true' != 5"); //Assertion fails

doVerbOnNoun('0'); //We verbed
console.assert(true == '0', "'true' != '0'"); //Assertion fails

To my mind, this is irrational, unsettling and in possible violation of the laws of gravity; yet, it had never occurred to me that an if('gimme shelter') statement would ever not be met as truthy. In fact, my mind was so far out of touch with the rules of the matrix, that I spent a few fevered seconds struggling with this paradox:

doVerbOnNoun({}); //We verbed
console.assert({} == true, "{} != true"); //Assertion fails
console.assert({} == false, "{} != false"); //Assertion fails

Clearly, loose truthy evaluation is not part of the algorithm of the single parameter if() statement. The multinational we can exercise some futility by instrumenting doVerbOnNoun with some diagnostics:

function doVerbOnNoun(aThing) {;

if(aThing) {
console.log('Verbing on ' + aThing);
} else {
console.log('Not verbing on ' + aThing);

console.log(!aThing, 'evaluating (!' + aThing + ')');
console.log(false != aThing, 'evaluating (' + aThing + ' != false)');
console.log(false != (false == aThing), 'evaluating (false != (false == ' + aThing + ')');
console.log(true == aThing, 'evaluating (' + aThing + ' == true)');


But none of the assertions align with the evaluation of the if() statement 100% of the time. So what is actually happening? Pure, unbiased, unmitigated, unabashed madness--that's what. Section 12.5 of the ECMAScript specification defines the if() statement as:

"The production IfStatement : if ( Expression ) Statement is evaluated as follows:
Let exprRef be the result of evaluating Expression.
If ToBoolean(GetValue(exprRef)) is false, return (normal, empty, empty).
Return the result of evaluating Statement."
What of ToBoolean, you ask (jaws clenched in fear, rage and agony)? It is sufficiently (albeit imperfectly) expressed as:

var ToBoolean = function (val) {
return (val !== false &&
val !== 0 &&
val !== '' &&
val !== null &&
val !== undefined &&
(typeof val !== 'number' || !isNaN(val)));

At least to the existential "us", this revelation is almost laughably ironic. The if() statement isn't loose or truthy and doesn't coerce type whatsoever, rather it simply casts whatever it is offered ToBoolean().

So ends this rather unsatisfying diversion into JavaScript. Please don't let this sully your feelings on the language. Restore your faith and go watch +Douglas Crockford's latest, most excellent talk on Monads and Gonads. It's worth every minute of your time.

You Might Also Like


Public Domain. All content published here is released into the PD, except when otherwise indicated. Powered by Blogger.


Popular Posts

Like us on Facebook

Flickr Images