Hints and tips
by Dan Mantyla, Simon Timms, Ved Antani
JavaScript: Functional Programming for JavaScript Developers
- JavaScript: Functional Programming for JavaScript Developers
- Table of Contents
- JavaScript: Functional Programming for JavaScript Developers
- JavaScript: Functional Programming for JavaScript Developers
- Credits
- Preface
- 1. Module 1
- 1. JavaScript Primer
- A little bit of history
- How to use this book
- Hello World
- Summary
- 2. Functions, Closures, and Modules
- 3. Data Structures and Manipulation
- 4. Object-Oriented JavaScript
- 5. Testing and Debugging
- 6. ECMAScript 6
- 7. DOM Manipulation and Events
- 8. Server-Side JavaScript
- 1. JavaScript Primer
- 2. Module 2
- 1. Designing for Fun and Profit
- 2. Organizing Code
- 3. Creational Patterns
- 4. Structural Patterns
- 5. Behavioral Patterns
- 6. Functional Programming
- 7. Reactive Programming
- 8. Application Patterns
- 9. Web Patterns
- 10. Messaging Patterns
- 11. Microservices
- 12. Patterns for Testing
- 13. Advanced Patterns
- 14. ECMAScript-2015/2016 Solutions Today
- 3. Module 3
- 1. The Powers of JavaScript's Functional Side – a Demonstration
- 2. Fundamentals of Functional Programming
- 3. Setting Up the Functional Programming Environment
- 4. Implementing Functional Programming Techniques in JavaScript
- 5. Category Theory
- 6. Advanced Topics and Pitfalls in JavaScript
- 7. Functional and Object-oriented Programming in JavaScript
- A. Common Functions for Functional Programming in JavaScript
- B. Glossary of Terms
- A. Bibliography
- Index
Here are a couple of brief tips to keep in mind about some of the patterns we've seen in this chapter:
- When implementing the interpreter pattern you may be tempted to use JavaScript proper as your DSL and then use the
evalfunction to execute the code. This is actually a very dangerous idea asevalopens up an entire world of security issues. It is generally considered to be very bad form to useevalin JavaScript. - If you find yourself in the position to audit the changes to data in your project, then the memento pattern can easily be modified to suit. Instead of keeping track of just the state changes, you can also track when the change was made and who changed it. Saving these mementos to disk somewhere allows you to go back and rapidly build an audit log pointing to precisely what happened to change the object.
- The observer pattern is notorious for causing memory leaks when listeners aren't properly unregistered. This can happen even in a memory managed environment such as JavaScript. Be wary of failing to unhook observers.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.