I'm missing some obvious joke...but why is he pronouncing it yava-script.
He's in character of it being 2035 and the pronunciation was lost/changed.
The Birth and Death of JavaScript [video]
21–30 of 236 posts
Re: The Birth and Death of JavaScript [video]
#22I'm missing some obvious joke...but why is he pronouncing it yava-script.
I thought it was supposed to be some future pronunciation thing, imagining the way languages evolve. I've seen SciFi movies where in the future english is heavily influenced by spanish.
Re: The Birth and Death of JavaScript [video]
#23For those unfamiliar, Gary Bernhardt is the same guy who did the famous "Wat" talk on JavaScript: https://www.destroyallsoftware.com/talks/wat
That was really funny. First time I've laughed all day. Thanks for sharing.
Re: The Birth and Death of JavaScript [video]
#24I wish some of those talks were available for purchase on their own and not in the season packets. Definitely a few I'd buy since I liked this talk and the demo on the site.
Guy has good vim skills for sure.
Re: The Birth and Death of JavaScript [video]
#25> xs = ['10', '10', '10']
> xs.map(parseInt)
[10, NaN, 2]
Javascript is beautiful.
Re: The Birth and Death of JavaScript [video]
#26> xs = ['10', '10', '10'] > xs.map(parseInt) [10, NaN, 2] Javascript is beautiful.
It's due to parseInt having an optional second parameter, the radix, and map passing the index as the second paramater, hence:
xs = [
parseInt('10', 0),
parseInt('10', 1),
parseInt('10', 2)
]Re: The Birth and Death of JavaScript [video]
#27> xs = ['10', '10', '10'] > xs.map(parseInt) [10, NaN, 2] Javascript is beautiful.
[deleted]
Re: The Birth and Death of JavaScript [video]
#28> xs = ['10', '10', '10'] > xs.map(parseInt) [10, NaN, 2] Javascript is beautiful.
It's due to parseInt having an optional second parameter, the radix, and map passing the index as the second paramater, hence: xs = [ parseInt('10', 0), parseInt('10', 1), parseInt('10', 2) ]
And since 0 is falsy we get 10 for base 0.
Re: The Birth and Death of JavaScript [video]
#29> xs = ['10', '10', '10'] > xs.map(parseInt) [10, NaN, 2] Javascript is beautiful.
There are so many good WTFs in JS, but this is not one. parseInt expects 2 arguments and Array.prototype.map provides 3 to the callback it is given. Both of these facts are very well documented and known.
var mappableParseInt = function(str){
return parseInt(str, 10);
};
['10', '10', '10'].map(mappableParseInt);
Re: The Birth and Death of JavaScript [video]
#30Earlier quoted context omitted.
It's due to parseInt having an optional second parameter, the radix, and map passing the index as the second paramater, hence: xs = [ parseInt('10', 0), parseInt('10', 1), parseInt('10', 2) ]
And since 0 is falsy we get 10 for base 0.
Which is odd. I wonder why they checked for falsiness and not the argument being undefined.