| Summary: | Like it or not, JavaScript is not going away. No matter what framework or "compiles-to-js" language or library you use, bugs and performance concerns will always be an issue if the underlying quality of your JavaScript is poor. Rewrites, including porting to the framework of the month, are terribly expensive and unpredictable. The bugs won't magically go away, and can happily reproduce themselves in a new context. To complicate things further, features will get dropped, at least temporarily. This book provides clear guidance on how best to avoid these pathological approaches to writing JavaScript. Bad code doesn't have to stay that way. And making it better doesn't have to be intimidating or unreasonably expensive.
|
|---|