"JavaScript in combat" reading notes

Is it true that every JavaScript book tells the history of JavaScript to clarify its relationship with Java? But it is also necessary to know the history of a language, and remember that the longer you look at the past, the farther you will see the future.

The creator of JavaScript is:Brendan Eich,1995 years of writing completed, the language was originally called Livewire, later renamed as LiveScript. As for why then became JavaScript, is not Java is very popular?

December 4, 1995, Netscape and Sun jointly released JavaScript.

In 1996, JavaScript was submitted to the ECMA (European Computer Manufacturers Association) for Standardization. JavaScript can be thought of as a standard implementation of ECMAScript.

Time Line :

version	Release date	based on	Netscape Navigator	Mozilla Firefox	Internet Explorer	Opera	Safari	Google Chrome
1.0	March 1996		2.0
1.1	August 1996		3.0		3.0
1.2	June 1997		4.0-4.05
1.3	October 1998	ECMA-262 1st edition/ecma-262 2nd Edition	4.06-4.7x		4.0
1.4			Netscape Server
1.5	November 2000	ECMA-262 3rd Edition	6.0	1.0	5.5 (JScript 5.5), 6 (JScript 5.6), 7 (JScript 5.7), 8 (JScript 6)	6.0, 7.0, 8.0, 9.0
1.6	November 2005	1.5 + array Extras + array and String generics + e4x		1.5			3.0, 3.1
1.7	October 2006	1.6 + Pythonic Generators + iterators + Let		2.0			3.2, 4.0	1.0
1.8	June 2008	1.7 + Generator expressions + Expression Closures		3.0		11.50
1.8.1		1.8 + Native JSON support + Minor Updates		3.5
1.8.2	June 22, 2009	1.8.1 + Minor Updates		3.6
1.8.5	July 27, 2010	1.8.1 + ECMAScript 5 Compliance		4	9	11.60

Early browser JavaScript compatibility is not very good, so often for a Web page to write several JavaScript code. IE is a big market, and Microsoft has developed its own JScript. "Browser sniffing" This is the first time I heard this noun, in fact, just a change of a noun, that is, the browser version of the detection, and then logical judgment, in order to reach the different browsers using different path response. This will be mentioned in the BOM model.

performance and memory issues with JavaScript :

This aspect is not very understanding, very few performance tests.

So the root of evil: the developer

Well, in fact this section is about the developer side, perhaps the browser will be very diverse, but the developer's features must be more than the browser. The difference between the code written by each developer can also be significant. You can look at the JavaScript coding style of the book bar.

Effects?

In this section, JavaScript can be used to achieve some of the cool effects, but these effects can really bring you efficiency, bring the click-through rate? Will it be in a flashy situation? To tell the truth, I have always been the pursuit of these special effects, I think can make these very cool, very powerful. But in the learning phase, you should put these aside first. A good special effect can improve the user's experience, but the fancy special effects, will let the human eye lose the focus of the webpage again.

maintenance of the code :

Since there is writing, there will be maintenance, good coding habits, can facilitate the maintenance of code. A bunch of messy code that might pay you a bigger price.

"JavaScript in combat" reading notes