There are a lot of these poor API design decisions in early JavaScript, which we... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		jdlshore on June 23, 2023 \| parent \| context \| favorite \| on: Why [“1”,“2”,“3”].map(parseInt) yields [1, NaN, Na... There are a lot of these poor API design decisions in early JavaScript, which we're stuck with due to the need for backwards compatibility. ("Don't break the web.") Modern JavaScript APIs tend to be pretty good. Fortunately, early JavaScript was also very small, so you mostly memorize the footguns (or use a linter) and you're good. This is one of them.

twelve40 on June 23, 2023 [–]

would a linter help here though? it seems to be a perfectly valid call here, except doing something unintended.

dragonwriter on June 23, 2023 | [–]

A linter would help, if you have a lint rule that requires a locally defined (regular or arrow) function and not a variable inside of map, filter, etc.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact