@sandfoxuk @chrisjenx There's really no excuse for leaving something like that broken. #mytwocents
-
-
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 Just look at PHP for example of inertia when it comes to fixing broken shizzle. It’s a sad story.1 reply 0 retweets 0 likes -
Replying to @sandfoxthat
@sandfoxuk
@sebinsua mm true. Guess that's the reason new Lang's are more popular. Python/Ruby/F# trying to learn from the past1 reply 0 retweets 0 likes -
Replying to @chrisjenx
@chrisjenx@sebinsua Lol, ruby is utterly fucked as a lang, python is stuck on 2.7. F# ? who cares/knows about it. clojure/go/rust/etc few2 replies 0 retweets 0 likes -
Replying to @sandfoxthat
@sandfoxuk
@sebinsua Agreed, but they are not mature enough (clojure being the exception, i think?)2 replies 0 retweets 0 likes -
Replying to @chrisjenx
@chrisjenx@sebinsua for really broken JS try this : [1,2,3].map(parseInt)2 replies 0 retweets 0 likes
@sandfoxuk @chrisjenx I like this too: [1,2,3,4,5,6,7,8,9,10,11,12,13].sort()
eh...
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.