@OsrsNeedsF2P@lemmy.ml to Programmer Humor@programming.dev • 1 year agoparseInt(5)lemmy.mlimagemessage-square65fedilinkarrow-up1506arrow-down16
arrow-up1500arrow-down1imageparseInt(5)lemmy.ml@OsrsNeedsF2P@lemmy.ml to Programmer Humor@programming.dev • 1 year agomessage-square65fedilink
minus-square@heavy@sh.itjust.workslinkfedilinkEnglish-3•1 year agoTheoretically, Javascript is an untyped language, so there aren’t supposed to really be static types. Giving type errors in this situation would be against design.
minus-square@heavy@sh.itjust.workslinkfedilinkEnglish5•1 year agoLol you’ll get no argument from me. It’s not my favorite language.
minus-square@bleistift2@sopuli.xyzlinkfedilinkEnglish6•1 year agoJavaScript has types and it does have type errors, for instance > null.foo Uncaught TypeError: null has no properties Please stop spouting nonsense on issues you know nothing about.
minus-square@heavy@sh.itjust.workslinkfedilinkEnglish-4•1 year agoDynamic types aren’t static types my man. I think you got some learning to do.
minus-square@heavy@sh.itjust.workslinkfedilinkEnglish0•1 year agoLol like facilitate versus effectuate
minus-square@zqwzzle@lemmy.calinkfedilinkEnglish-2•1 year ago Theoretically, Javascript is an untyped language… Function only handles string arguments correctly. Wat.
Theoretically, Javascript is an untyped language, so there aren’t supposed to really be static types. Giving type errors in this situation would be against design.
Maybe the design is bad, then.
Lol you’ll get no argument from me. It’s not my favorite language.
JavaScript has types and it does have type errors, for instance
> null.foo Uncaught TypeError: null has no propertiesPlease stop spouting nonsense on issues you know nothing about.
Dynamic types aren’t static types my man. I think you got some learning to do.
You did say untyped though.
Lol like facilitate versus effectuate
Function only handles string arguments correctly. Wat.