DEV Community

loading...

Why do many Javascript libraries or documentations keep using callback, var, == or function keywords?

patarapolw profile image Pacharapol Withayasakpunt ・1 min read

Despite being recently updated. Without support for arrow functions, of course.

Or, the authors are experienced and immune to callback hell? No, the libraries aren't for noobs.

They are just being experienced with the old ways, and wouldn't create bugs, anyways.

Discussion (1)

pic
Editor guide
Collapse
lexlohr profile image
Alex Lohr
  • callback: a many libraries aim to be isomorphic, i.e. work both on node as well as in the browser, the former coming with a strong preference for callback patterns (and a utility to promisify functions adhering to that pattern).
  • var: if you want to support browsers older than IE11, you'll have to use var instead of const and let; of course, you can use a transpiler to support them, but then you'll give up part of the control you have over your code and not everyone wants that.
  • ==: In some cases, you explicitly want your comparisons to coerce other types; yes, you could manually coerce them and use a typesafe comparison, but you don't need to.

You could also ask why people are using || if ?? is available. Sometimes, the choice was made consciously. Also, many of these libraries are around for longer than 5 years and thus had no arrow functions when the documentation was written.