— Even the first chapter has so much to teach
Also even more js devs could benefit from learning proper OOP best practices such as unobtrusive js, and the law of demeter
— Is is VERYYYYY easy to bypass the law of demeter in js, by nature of js scope
— All too often js devs take advantage of the antipattern js allows, and that is another contributor to bad js in the wild imo
— A great basic example, which is the one I see most commonly, is event listeners (or rather lack of them) in favor of element attributes like
— This is incorrect and should never be used
<input type="text" name="date" onchange="validateDate()" />
— I read parts of it at a library and decided it was a bit below my skill level, but I found it to be very well written
A powerful, object-based, interpreted scripting language, created by Brendan Eich, most commonly embedded directly into HTML web pages to manage client-side interaction.
— The should part is quite subjective.
— Heavy use of FP constructs can make code hard to parse unless the actions are very clearly defined.
— Which is why you encapsulate those moving parts in OOP