@sebinsua because someone derped a while back :: http://www.2ality.com/2013/10/typeof-null.html …
-
-
Replying to @sandfoxthat
@sandfoxuk
@sebinsua I'm sorry this basically means JS as a Lang is fundamentally broken?!?1 reply 0 retweets 0 likes -
Replying to @chrisjenx
@chrisjenx@sebinsua JS was written in about 5 days, kind of to be expected. That bug is now a feature :-)1 reply 0 retweets 0 likes -
Replying to @sandfoxthat
@sandfoxuk
@chrisjenx They should add a new operator with fixed behaviour, and then make 'use strict' give you a slap for using 'typeof'.2 replies 0 retweets 0 likes -
Replying to @nouswaves
@sandfoxuk
@chrisjenx There's really no excuse for leaving something like that broken.#mytwocents1 reply 0 retweets 0 likes -
Replying to @nouswaves
@sebinsua@chrisjenx broken, possibly. but also now expected behaviour for a bazillion websites / libraries / apps2 replies 0 retweets 0 likes -
Replying to @sandfoxthat
@sandfoxuk
@chrisjenx Oh, I'm not saying I would get rid of the old 'typeof'. That can say. I'd add a new 'typeof' with fixed behaviour.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@sandfoxuk
@chrisjenx And then I would be like "hey guys, I'm deprecating the old typeof and it will stop working in 20 years."1 reply 0 retweets 0 likes -
Replying to @nouswaves
@sandfoxuk
@chrisjenx Then you can just leave it to engineers and creators of jshint/jslint to stop smart people from using the old typeof.3 replies 0 retweets 0 likes -
Replying to @nouswaves
@sebinsua@chrisjenx but seriously, this is a non-issue in the grand scheme of Javascripts actual problems,1 reply 0 retweets 0 likes
@sandfoxuk @chrisjenx True. It's just glaringly broken. It's beyond even type-coercion brokenness.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.