Things to avoid in JavaScript (the bad parts)
A quick list of things to avoid when writing JavaScript code
React Masterclass
Launching on November 4th
- Avoid creating a new object by using
new Object(). Use the object literal syntax{}instead. - Same thing for arrays, favor
[]overnew Array(). - Avoid blocks except where statements require them (
if,switch, loops,try). - Never assign inside an
ifofwhilestatements condition part - Never use
==and!=. Use===and!==instead. - Never use
eval. Why? It has performance issues (it runs the interpreter/compiler), it has security issues (code injection if used with user input), difficulties in debugging. - Never use
with, as it modifies the scope chain and can be a source of confusion. - Always pass functions to
setTimeoutandsetInterval - Never use
Arrayas an associative arrays, useObjectinstead. The part of theArrayobject that provides that functionality is in fact provided by theObjectprototype, so you could really have used aDateobject for that same thing. - Don’t use
\at the end of a string to create a multiline string, it’s not part of ECMAScript. Use string concatenation' string1 ' + ' string2 'instead - Never modify the prototypes of the built-in objects
ObjectandArray. Modify other prototypes of other objects such asFunctionwith caution as it could lead to bugs hard to debug.
→ Get my JavaScript Beginner's Handbook
I wrote 20 books to help you become a better developer:
- JavaScript Handbook
- TypeScript Handbook
- CSS Handbook
- Node.js Handbook
- Astro Handbook
- HTML Handbook
- Next.js Pages Router Handbook
- Alpine.js Handbook
- HTMX Handbook
- React Handbook
- SQL Handbook
- Git Cheat Sheet
- Laravel Handbook
- Express Handbook
- Swift Handbook
- Go Handbook
- PHP Handbook
- Python Handbook
- Linux/Mac CLI Commands Handbook
- C Handbook