Re:JavaScript in 2015
by beejiu on Wednesday January 07, 2015 @03:41PM
(#8853163)
All you have done is used a function without understanding what it was doing, or reading the documentation. Most JS developers know how parseInt works, and even if they run into this problem, would quickly discover the cause. I don't see how this is a flaw of Javascript; it could happen to a developer of any language, if their strategy is 'well, it looks like it'll work'.
[ Parent
| on HN ]
Re:JavaScript in 2015
by sarciszewski on Wednesday January 07, 2015 @04:15PM
(#8853359)
> All you have done is used a function without understanding what it was doing, or reading the documentation
These aren't my examples. I haven't done anything. I credited the person who provided them: Gary Bernhardt.
https://www.destroyallsoftware.com/talks/wat
https://www.destroyallsoftware.com/talks/the-birth-and-death...
Next time before you make an accusation, reread the post before pressing the reply button.
Re:JavaScript in 2015
by prezjordan on Monday January 12, 2015 @07:00PM
(#8877291)
Nope. Behavior should be pretty straight-forward, I shouldn't have to load up the docs to convert something to an integer.