How often do you hear people say things like this? "Our JavaScript is a mess, but we’re thinking about using [framework of the month]."
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.
The other popular method of fixing your JS is playing “JavaScript Jenga,” where each developer slowly and carefully takes their best guess at how the out-of-control system can be altered to allow for new features, hoping that this doesn’t bring the whole stack of blocks down. 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.
You can read this ebook online in a web browser, without downloading anything or installing software.
This ebook is available in file types:
This ebook is available in:
After you've bought this ebook, you can choose to download either the PDF version or the ePub, or both.
The publisher has supplied this book in DRM Free form with digital watermarking.
You can read this eBook on any device that supports DRM-free EPUB or DRM-free PDF format.
The publisher has supplied this book in encrypted form, which means that you need to install free software in order to unlock and read it.
To read this ebook on a mobile device (phone or tablet) you'll need to install one of these free apps:
To download and read this eBook on a PC or Mac:
The publisher has set limits on how much of this ebook you may print or copy. See details.