Format: PaperbackChange
Price:$30.94+ Free shipping with Amazon Prime
There was a problem filtering reviews right now. Please try again later.
on December 29, 2014
I've been a professional web developer for 18 years and have always read every JavaScript book, blog, post and ebook I could find. A junior web developer on staff asked me if I could recommend a good JavaScript book. I recommended Maintainable JavaScript by Nicholas Zakas, JavaScript Patterns by Stoyan Stefanov and this David Flanagan gem as the first priority and gave it as a welcome aboard gift. I don't care how good at Googling JavaScript questions you are, if you read this book cover to cover, you'll keep thinking, "I didn't know you could do that!" I highly recommend it to web devs of any level.
on September 7, 2016
I spent one month finishing reading this book. I would say I feel so good after reading it and have more confidence in talking about Javascript as a programming language (not as a tool). Before this book, I also read "Beginning to Javascript", so I had certain preparation to read this heavy-content book. "Beginning to Javascript" teaches me to use JavaScript as a tool and I can quickly building something in JS after reading it. But this book is different, it fulfills my needs to learn and know JavaScript as a programming language that worths certain respect.
If you think that this book is full of theory but no practice so it does not worth a read, I have nothing to say as different programmer learn to program and know about programming languages in different ways. This book is for those who want to know more about JavaScript and get inspired.
If you think that this book is full of theory but no practice so it does not worth a read, I have nothing to say as different programmer learn to program and know about programming languages in different ways. This book is for those who want to know more about JavaScript and get inspired.
on April 4, 2017
This is a good reference but I rarely pick it up. The latter part of the book is a huge index which you can find online anyway.
I didn't enjoy this book because it focused too much on the mechanics and code listings. It didn't have enough information on the background and evolution of how javascript developers have progressed in thinking over the years. For that reason, I prefer and recommend Professional JavaScript for Web Developers. Doubly so if you are a backend engineer or already are versed in at least one language.
I didn't enjoy this book because it focused too much on the mechanics and code listings. It didn't have enough information on the background and evolution of how javascript developers have progressed in thinking over the years. For that reason, I prefer and recommend Professional JavaScript for Web Developers. Doubly so if you are a backend engineer or already are versed in at least one language.
on January 10, 2014
I bought this book because I wanted a comprehensive introduction to JavaScript, rather than picking up bits and pieces from the web. I've programmed in other languages before so the first several chapters were no problem, even if the concepts were presented very much out of order. I'm trying to understand how OO programming works in JavaScript now, and the book is not making it easy. For reasons unclear to me, Objects and Classes are introduced in two separated chapters, separated with two unrelated chapters in between. The chapter on Objects inundates you with details of how objects differ in ECMAScript3 versus ECMAScript5 rather than giving an intuitive introduction to how to work with objects. I felt bewildered and overwhelmed, but since the Objects chapter kept saying that topics would be explained in the Classes chapter, I still had some hope. Now, reading the Classes chapter, the text keeps referring me back to the Objects chapter for explanations of prototypes, constructors, etc. I'm not amused.
Bottom line: if you are looking for a noob-friendly primer on how OO programming works in JavaScript, look elsewhere. Otherwise, the book so far appears to be very comprehensive and introduces several "idiomatic" techniques that are probably important to at least be aware of if you are reading other's code.
Bottom line: if you are looking for a noob-friendly primer on how OO programming works in JavaScript, look elsewhere. Otherwise, the book so far appears to be very comprehensive and introduces several "idiomatic" techniques that are probably important to at least be aware of if you are reading other's code.
on February 24, 2014
I thought I had kept up with things since the last version. This book clued me in to new, simpler techniques becoming practical solutions only now - now that IE7 is so clearly on the way out.
Much of the book was re-written. There were a few issues that remained a bit elusive after reading the previous version (V5) and V6 cleared them up for me.
After studying chapter 15 on scripting documents, I stopped the press and made a number of important updates to my utilities file - streamlining functions that heavily supported IE 7. I changed a number of my websites to no longer support IE7 - this book gave me the information and courage to do so (the author did not suggest such a move, but it only made sense to me after getting myself up-to-snuff on the modern DOM). My code is now faster and leaner and much much much easier to follow (and debug if ever necessary) by using up-to-date basic dom methodologies such as:
A. Element.prototype to add some important/simple dom navigation methods to all elements (next(), previous() ..)
B. cssClass property to more easily, efficiently, and accurately deal with element classes (whereas I had a lot of code to do these functions and avoid RegExp for efficiency, now my methods simply pass cssClass with a simple RegExp as a fallback for IE8/9 which don't support cssClass. My perspective now is to NOT provide robust fallback for old IE, but only minimal anticipating users will make the jump from IE8 directly to IE 10/11 when their old PCs finally crap out (for those who use IE).
C. use of "data-" element attributes, which allow HTML to validate. I used to wrestle with confusing multiple classes to pass data so my html would validate - or I'd write special server / js scripts to attach data to elements as JS objects after the page loaded.
These examples aren't particularly the new sexy HTML5 initiatives, but without this book it might have taken me years to learn of them and to understand them enough to actually put them into play. And by the way, the book does a good job explaining the many HTML 5 initiatives - but I would first scan the pages to see if they were practical for my use and whether they were widely supported. But it's the small, detailed, practical things used in work-a-day scripting that makes this book so important to me.
I can't say this is a book for beginners only because of its length (1000+ pages) - but after learning JS on my own I wish I had read V5 of this book first as the others I read were all either somewhat outdated or too skimpy in important areas. This is really the only one that I read that goes into detail on the practical application of JS in client side scripting. It's the only JS book I use a reference.
My only criticism is that the book includes an entire chapter on jQuery (65 pages). I don't see the need for re-learning jQuery given browsers are moving along nicely toward standards compliance anyway. But the book would still weigh almost as much without the jQuery chapter.
Much of the book was re-written. There were a few issues that remained a bit elusive after reading the previous version (V5) and V6 cleared them up for me.
After studying chapter 15 on scripting documents, I stopped the press and made a number of important updates to my utilities file - streamlining functions that heavily supported IE 7. I changed a number of my websites to no longer support IE7 - this book gave me the information and courage to do so (the author did not suggest such a move, but it only made sense to me after getting myself up-to-snuff on the modern DOM). My code is now faster and leaner and much much much easier to follow (and debug if ever necessary) by using up-to-date basic dom methodologies such as:
A. Element.prototype to add some important/simple dom navigation methods to all elements (next(), previous() ..)
B. cssClass property to more easily, efficiently, and accurately deal with element classes (whereas I had a lot of code to do these functions and avoid RegExp for efficiency, now my methods simply pass cssClass with a simple RegExp as a fallback for IE8/9 which don't support cssClass. My perspective now is to NOT provide robust fallback for old IE, but only minimal anticipating users will make the jump from IE8 directly to IE 10/11 when their old PCs finally crap out (for those who use IE).
C. use of "data-" element attributes, which allow HTML to validate. I used to wrestle with confusing multiple classes to pass data so my html would validate - or I'd write special server / js scripts to attach data to elements as JS objects after the page loaded.
These examples aren't particularly the new sexy HTML5 initiatives, but without this book it might have taken me years to learn of them and to understand them enough to actually put them into play. And by the way, the book does a good job explaining the many HTML 5 initiatives - but I would first scan the pages to see if they were practical for my use and whether they were widely supported. But it's the small, detailed, practical things used in work-a-day scripting that makes this book so important to me.
I can't say this is a book for beginners only because of its length (1000+ pages) - but after learning JS on my own I wish I had read V5 of this book first as the others I read were all either somewhat outdated or too skimpy in important areas. This is really the only one that I read that goes into detail on the practical application of JS in client side scripting. It's the only JS book I use a reference.
My only criticism is that the book includes an entire chapter on jQuery (65 pages). I don't see the need for re-learning jQuery given browsers are moving along nicely toward standards compliance anyway. But the book would still weigh almost as much without the jQuery chapter.
on April 18, 2017
A good supplement to learning Javascript from OReilly. You can use it as a reference or use it as a guide to JavaScript. Like most of the OReilly books the quality is high, the content is relevant and the layout is appropriate,
on August 26, 2013
As the subtitle indicates, this work is definitive. Be prepared to find yourself sinking or swimming right from the start, as the material gets technical from page viii and never looks back. Be advised: Flanagan is not a flowery, anecdotal writer. But he appears to be thorough. Stick with it. The payoff is enormous, as obscure concepts (for a newbie like me) discussed in the first hundred pages or so are clarified satisfactorily later on. This is not only a book about JavaScript, but also a commentary on how programming (and its language component) as a concept has evolved in reaction and relation to the internet. Coming from a Visual Basic, standalone executable perspective, I found this approach very helpful in augmenting my knowledge base.
Programming fundamentals from a JavaScript perspective are carefully explained, although some patience may be required from the reader, especially if they have little or no exposure to the C-family language. Again, stick with it; Flanagan delivers on that subtitle. And despite the claim that JavaScript, by its nature, might forever defy a true reference, there's one in here, and that was one of the reasons I decided to buy this book. In fact, there are several references inside, covering both client-side and server-side JavaScript components. Very handy. There's even a chapter on jQuery, comprehensive enough to be its own book (see: jQuery, the Pocket Reference, also by Flanagan).
Occasionally I struggle with some of the material presented, but I'm guessing that's because of my lack of exposure to anything C++, rather than the author's approach/delivery. In fact, Flanagan seems to anticipate a little struggling with concepts, and frequently (enough) slows the pace down so that dinosaurs like me can stay caught up, focused, and moving forward.
This might be a 5-starred book, but since I haven't finished it in the 30 days since purchase, it gets stuck with 4 stars for now. Nonetheless, one might ask: is David Flanagan the NEW Danny Goodman?? BUY RECOMMENDATION
Programming fundamentals from a JavaScript perspective are carefully explained, although some patience may be required from the reader, especially if they have little or no exposure to the C-family language. Again, stick with it; Flanagan delivers on that subtitle. And despite the claim that JavaScript, by its nature, might forever defy a true reference, there's one in here, and that was one of the reasons I decided to buy this book. In fact, there are several references inside, covering both client-side and server-side JavaScript components. Very handy. There's even a chapter on jQuery, comprehensive enough to be its own book (see: jQuery, the Pocket Reference, also by Flanagan).
Occasionally I struggle with some of the material presented, but I'm guessing that's because of my lack of exposure to anything C++, rather than the author's approach/delivery. In fact, Flanagan seems to anticipate a little struggling with concepts, and frequently (enough) slows the pace down so that dinosaurs like me can stay caught up, focused, and moving forward.
This might be a 5-starred book, but since I haven't finished it in the 30 days since purchase, it gets stuck with 4 stars for now. Nonetheless, one might ask: is David Flanagan the NEW Danny Goodman?? BUY RECOMMENDATION
on March 15, 2012
Keep in mind I'm writing this review and I'm only 70 pages into this monster (plus some random skimming)
This book seems to be highly recommended by all the big and well known names in JS Development.
Having worked through a few substandard JS books (which there seems to be plenty of), I decided to spring for it. I'm blown away with how comprehensive this thing is. I wish all my college textbooks were up to this standard. It's true that this isn't for someone new to programming, or even someone new to JavaScript. [I found "Eloquent Javascript" (which is a free online book) to be a good starter book. I say this after having looked at the head start book (complete rubbish) and Wrox's Beginning JavaScript (crap).]
Anyway,it's dense and not something you're going to get through fast.
I'm taking the approach my Calculus Professor recommended for 'reading a math text'. You read a math text with a pencil and paper. When presented with a proof you should work through it step by step with pencil and paper so that you can see the logic behind it, then try it out with some examples. Well, instead of pencil and paper I have my laptop next to me with the cloud9 IDE up (a great and simple browser based editor I'm growing fond of). As each new concept (at least, each concept that is new to me) is presented I try it out on the editor and print the output to the console. As I work through it and grasp what it does I "poke it with a stick" by trying some different things with it. I already feel like I have a better grasp of the basics then I ever did with my previous experiences.
I'm sure this book isn't perfect...I don't think that's possible in the world of technology books. But it's substantially higher quality than many I've read including $180 college texts.
This book seems to be highly recommended by all the big and well known names in JS Development.
Having worked through a few substandard JS books (which there seems to be plenty of), I decided to spring for it. I'm blown away with how comprehensive this thing is. I wish all my college textbooks were up to this standard. It's true that this isn't for someone new to programming, or even someone new to JavaScript. [I found "Eloquent Javascript" (which is a free online book) to be a good starter book. I say this after having looked at the head start book (complete rubbish) and Wrox's Beginning JavaScript (crap).]
Anyway,it's dense and not something you're going to get through fast.
I'm taking the approach my Calculus Professor recommended for 'reading a math text'. You read a math text with a pencil and paper. When presented with a proof you should work through it step by step with pencil and paper so that you can see the logic behind it, then try it out with some examples. Well, instead of pencil and paper I have my laptop next to me with the cloud9 IDE up (a great and simple browser based editor I'm growing fond of). As each new concept (at least, each concept that is new to me) is presented I try it out on the editor and print the output to the console. As I work through it and grasp what it does I "poke it with a stick" by trying some different things with it. I already feel like I have a better grasp of the basics then I ever did with my previous experiences.
I'm sure this book isn't perfect...I don't think that's possible in the world of technology books. But it's substantially higher quality than many I've read including $180 college texts.
on July 1, 2012
As a C#/C++ developer I bought this book to learn basics of JavaScript. I don't plan to develop Web apps, but because JavaScript effectively became 'the language of the web' it's nearly inevitable to know at least basic syntax and semantic of this language.
In my opinion, this book is the same to JavaScript as Bjarne Stroustrup's The C++ Programming Language to C++. The book is divided into 4 parts. First part is dedicated to core JS features. Writing style, depth of explanations, examples, all strongly resemble Stroustrup's book. Flanagan goes into great depth, he explains all problematic parts of JS itself (honestly JS syntax and semantic is sometimes bizarre) and differences between JS implementations. Especially the attention he pays to JS semantic 'quirks' (for instance automatic conversions of numbers, arrays, objects, string) that are so different to C-like languages was very useful for me. Also I like that sample programs didn't bother with any HTML code (the results are just written in comments). It's a great idea not to mix HTML and JS in these early stages of study. Only thing I didn't like was Chapter 6. I think author should have merged this chapter with chapter 9 and he could have presented object-oriented aspects of JS (especially prototype inheritance) together with the presentation of objects.
Second part is all about JS integration with web browsers. Once again author gives in-depth coverage, with many details about differences between browser implementations. Many samples contain utility functions that helps you to overcome these disparities. Chapter 19 contains good intro into jQuery and last chapter covers some new HTML 5 features like client side DB or Web Sockets.
Last two parts (about 300 pages) are JS references covering all important JS functions and classes. To be honest, this part of book was unnecessary for me. If you have Internet, you don't need this printed version of JS reference. It just makes the book thicker and heavier.
To sum up. JS The Definitive Guide is useful book for experienced developers who know some other object oriented language and want to learn JS. It's not the best IT book I have ever read but still it gave me good intro into JS.
In my opinion, this book is the same to JavaScript as Bjarne Stroustrup's The C++ Programming Language to C++. The book is divided into 4 parts. First part is dedicated to core JS features. Writing style, depth of explanations, examples, all strongly resemble Stroustrup's book. Flanagan goes into great depth, he explains all problematic parts of JS itself (honestly JS syntax and semantic is sometimes bizarre) and differences between JS implementations. Especially the attention he pays to JS semantic 'quirks' (for instance automatic conversions of numbers, arrays, objects, string) that are so different to C-like languages was very useful for me. Also I like that sample programs didn't bother with any HTML code (the results are just written in comments). It's a great idea not to mix HTML and JS in these early stages of study. Only thing I didn't like was Chapter 6. I think author should have merged this chapter with chapter 9 and he could have presented object-oriented aspects of JS (especially prototype inheritance) together with the presentation of objects.
Second part is all about JS integration with web browsers. Once again author gives in-depth coverage, with many details about differences between browser implementations. Many samples contain utility functions that helps you to overcome these disparities. Chapter 19 contains good intro into jQuery and last chapter covers some new HTML 5 features like client side DB or Web Sockets.
Last two parts (about 300 pages) are JS references covering all important JS functions and classes. To be honest, this part of book was unnecessary for me. If you have Internet, you don't need this printed version of JS reference. It just makes the book thicker and heavier.
To sum up. JS The Definitive Guide is useful book for experienced developers who know some other object oriented language and want to learn JS. It's not the best IT book I have ever read but still it gave me good intro into JS.
