The direction of the way is not the direction is blindfolded donkey in situ one year experience mixed ten years said is very good. You must paste the copy down article (Masaki)

For more than two years, my book finally into print without published. Should be in all aspects of the requirements, write a soft article, a grand introduction of this book on the programmer's money to help you and the reading order and other questions. As the first book to talk about the front-end framework, it is filled with a lot of unheard-of knowledge, the knowledge of 50% only issue on GitHub, tell a variety of hidden browser compatibility problems and a variety of magical repair solutions, or some dangerous but beautiful black magic, another 50% I was in the middle of the night sleepwalking some Daniel (not confined to English, Japanese, Russian, Korean, etc., different language people, subject to their grammatical structure, their thinking loop is different from us, given the answer is sometimes really simply astounding) of the blog or the site glimpses of the magical stuff. After I wrote the DOM framework, the mass Framework (DOM framework is the old-fashioned pyramid-based big-class framework, the mass framework is an open frame with an AMD loader, then Avalon, is a ghostly layered framework of the MVVM framework, full of black magic, after the establishment of a complete knowledge tree, began to frenzy like the conquest of the six countries after the Qin King, keen to collect all kinds of treasures in my blog-you see the part, just my unpublished one-tenth, this book will be added to the other two-tenths.

In fact, the world is wonderful, when you level up, even if you do not want to continue, the world also pushes you forward. Like jQuery1.3 through sizzle big success, become the star of the world, even if John Resig want to let go, but so many pull request, it can only from better become more good! Three years ago, when I wrote more than 300 blogs, the publishers had come to the door. In that six months, a total of three or four to find me, let me see the front-end hope. So my focus shifted from Ruby slowly to JavaScript. After I joined the Grand Innovation Institute, I had ensured that I was able to hold on to the big topic of JavaScript Framework design and signed up to write a book. However, in the original directory I submitted to the publishing house, I had a more magnificent goal, including drag and drop components, routing system, and various UI components, but finally because of the space problem, I have to say sorry.

Wild hope is always constrained by reality, Alexander wants to prove the world, but his HP is so short, can not afford to travel long distances. The Entity book and the blog is different, it must form a system, the style also has the request, cannot too colloquial, what joyful sorrow must collect, the straight face Turkey to everybody to preach. Typos also want to sepulchres a bit, although I find a lot of master reviewer. Unfortunately, all of them write round eyes, automatically filter out typos, and ultimately let the publishing house Zhang Tao greatly help deal with the majority of typos and wrong sentences, too professional things he can do nothing, I hope it does not affect reading. Fortunately, the great God contributed a lot of cold addiction useful knowledge points, so that the book to enrich a lot of, so just a change and change, three times four, resulting in more than two years before the turnaround. In the grand creation of the hospital, constantly someone (colleague or group of friends) asked me when the book came out, someone half a year to get a copy. I'm finally not bothered about the problem today.

=============================================================================================================== =====================================

In the continuation of this soft article, my mind is really flashing a lot of words, what cathedral and market, build wheels and dry, corporate interests and personal growth ... Come on.

The cathedral and the bazaar say how to build a software engineering, is the cathedral-style absolutism or open-ended crowdsourcing way to let everyone contribute source code. The former, to ease a little, is heroism, jquery to John Resig, node. js to Ryan Dahl, their single horse to create a new world. The latter, the most outstanding Representative is Linux. But in this world of mutual immersion, absolute things do not exist. jquery and node. JS are now also in the effort of a multitude of contributors, who are heading for the new destination. At home, you know, everyone is pretentious, at first you can only be a alone. Only after you have truly become a beacon of character, can people follow.

The issue of making wheels and dry also has been noisy many times on Sina Weibo. There is a software design principle called dry, to prevent members of the group at random to clone code, or unknowingly repeated the invention of similar functional modules. For the benefit of the company, but also reluctant to give time to build their own wheels, the Internet to find a jquery plugin. Therefore, small in the company's page is very scary, allow a large number of third-party plug-ins, and relatively, big Ali can use the basic self-made, this is the guerrillas and the regular army of the difference. From the domestic perspective, the most important JS companies are also precisely the big Ali, they have the most massive excellent front-end team (more than 700 people), small companies or a front-end to 20 back-end rhythm. What do you do with such a lot of tricks? Build the wheels! Of course, this is not what a wheel represents, it involves a whole set of toolchain, the goal is to achieve the front-end automation integration deployment. Writing frames and UI components is one of the few links, which is what people can understand, more tall things, big companies will not be public. But you have at least the ability to create UI components that will allow you to touch the underlying tools.

Corporate interests and personal growth, not to mention. Only short-sighted companies can write code with no-brand components. Big companies have already prepared a good thing for you. Your task is to grow to the point where you have to write UI components, get into the architect, and do more preparation for your company's future challenges. HTML5 for the average person, seems to be very distant things, but big companies have already had a lot of people use it to make many good things, for the company's products user experience. In order to accumulate this strength, you have to secretly put your own effort to write a set of things. Before someone else wrote the pop-up layer, Rich text editor, syntax highlighting plugin ... You can't have less, so you can get access to native APIs and knowledge points that you couldn't touch before. such as the pop-up layer about the vertical center of the CSS Knowledge points, select penetration problem, Rich Text editor to the IFRAME Knowledge points, range and Selection object knowledge points, syntax highlighting is your regular big test! If you write business code, you write for ten years, the level is still like that. So there's a saying-"spend a year in ten years."

Recently saw a terrible thing on Weibo:

"An insane programmer I know,"http://t.cn/8sinEOr , a programmer who had a mental disorder in our company not long ago. He went into the manager's office and began to shout and say something strange. If I didn't know him as much as I knew myself, I would think he was stoned. But the truth is he's insane!

He is the most diligent employee I have ever seen in the programming industry. He often works overtime after work, and on weekends he is always on call when managers need hands to handle emergency work. At this stage, the company does not make money, the boss needs to complete the project as soon as possible, so any customer anxious software development will be automatically assigned to him. He was happy to devote himself to finishing the job exactly the way the boss liked it.

"I am strong, I am efficient, I should be the company's key figures", in fact, that is wrong, irreplaceable is the most important. If the "hard" to increase the irreplaceable, the role is negligible, or rely on the "high threshold." The more skilled engineers I know, the more technically good engineers will become aware of this problem, and then do some "deep" development, which is the self-protection of engineers. It's a lame excuse to say what it's like to be a career-changing 30-year-old.

The ancients said-"There is no foresight, there will be immediate worries". You usually have so much free time, why not try to improve your level. Do not read the master's frame carefully, do not write a framework of their own. Remember when I was in the blog propaganda my frame, by some jealous person scold a getting yelled at, two years past, he disappeared, and I, from a company's core front-end into another company's core front-end, is now where the network of front-end architects. So believe in yourself! Do not be afraid of that, there is effort on the return!

Come back to say my book, the front-end knowledge point is very complicated. But knowledge is only strung together, and forming a knowledge tree is your own. Now the book on the market, basically copied to copy, or in accordance with the old method of teaching people, beginning always a historical review, then a variety of data types introduced, then the grammar (conditional branch, Loop Branch), and finally a few "real cases." This is too stuffy for the front end of the 90% halfway decent. And the front end is not just JavaScript, JavaScript is cement, or it's stored like a chemical molecule, and we're working to build a whole building! Only the physical level of what the naked eye sees is the protagonist. They are the focus of the book, Dom and BOM. JavaScript addresses the notorious compatibility issues of the front-end by entering different branches through feature detection or parameter transfer. This book introduces a lot of such black magic, how to know that the current browser is to support this event? Why hijack this here? How to get the selector engine to run faster. So this one question, then dissolve the cost of the book introduces the knowledge points, what AMD loader, selector engine, batch generation of a bunch of element nodes ...

All front-end frameworks face the same problem, and the difference is the level of resolution. So prototype died, jquery fire. Angular broke out and jquery was silent! The chapters of this book are written in the order in which a multi-file framework is written. The first must be the seed module, which defines the frame's name and version number, with some of the most core methods, and the loader. Then through the loader, add some common tool modules, the JavaScript language to expand and repair. After the data cache what, then is the main course, a variety of DOM problems, node Ah, style Ah, events ah, animation ah ... Finally, MVVM, the most powerful front-end solution in the current scenario. By introducing two-way binding and layered architecture, the front-end development is completely out of the DOM.

You may have had a passion, you have had a dream, but when your KPI Check point is PM those ridiculous change to change the function point, many fiery flames will also be extinguished. So you have to get something out and try to climb up. is to waste life in overtime, write business every day, or focus on the development of the bottom frame, for a problem and distress, is entirely in your an idea away. "It is the gold that always shines," or "the stone will not shine," and it is entirely in your an idea away. This book will give you a chance and a lot of skill points to open up a beautiful new world, providing an X-year opportunity to prepare for a rapidly rising channel.

Some people may think it is expensive, and some people are afraid that they can not understand so "tall" things. Let me tell you a story.

An insect-like man made such an experiment: he put the flea in his open bottle and jumped out immediately. When the bottle is covered, the flea still tries to jump out of the bottle, and it constantly hits the inside of the bottle. One hours later, he was still jumping like that. Almost three hours later, it was still jumping, but it no longer hit the cap, when it jumped to the height of about 1 centimeters from the bottle, and every time it is so. At this time, the bottle cap was taken off, but the flea did not jump out of the bottle, it still kept the height of the bottle cap, no longer jump out of the bottle.

Similarly, if you, always too expensive that expensive, you do not try to change the status quo, after a period of time, you will be accustomed to, will be satisfied with poverty. Like a flea in a bottle, he is always trapped in a bottle.

Afraid that they can not understand this thing, although it is a rational consideration, but as long as the person will encounter bottlenecks, but the problem is how to break through the bottleneck. Caps are not always covered, there are opportunities you have to seize!

I also graduated from the school to find a job, down to a year as a security guard. But I believe that "gold will always shine," I would blockbuster, I am just a wounded wolf, I will not be the fate of the surrender of domestication. So roar with me--

The Nameless flower of life has been ravaged by the fall of the bird is anxious to be the wind to pray, but there will be no change if you want to change, please start and fight it. We laughed at the attack of the swine, the animal-like peace, the false prosperity please give to the death of the Hungry Wolf to freedom!               ... --Attack on the giant op "red lotus bow vector"

=============================================================================================================== =====================================

Here is the list of books:

Prologue section 1th frame and Library 2nd section JavaScript Age Division 3rd section JavaScript Framework Classification 4th section JavaScript Framework main functions 1th Chapter seed Module 1th section namespace 2nd Section object extension 3rd section array 4th section type decision 5th section Domready 6th conflict-Free handling 2nd Module loading System 1th section AMD specification 2nd section Loader path of the Discovery 3rd section require method 4th section define method 3rd Chapter Language Module 1th section string extension and Repair 2nd section array extension and Repair 3rd section Extension and repair of Values 4th section extension and repair of section 5th date Extension and Repair 4th chapter browser sniffing and feature detection 1th section determining browser 2nd section Event support detection 3rd section Style Support Reconnaissance 4th section jquery The meaning of some commonly used features 5th Chapter Factory 1th Section JavaScript supports class 2nd section 2.1 of the implementation of various types of Factories P.js Section 2.2 JS. Class 2.3 simple-inheritance Section 2.4 def.js 3rd ES5 The impact of attribute descriptors on OO Libraries Chapter 6th selector engine 1th section browser built-in method of finding elements 2nd section getelementsbyselector 3rd section The selector engine involves a knowledge point in the 4th section of the general function involved by the Selector Engine section 4.1 isxml section 4.2 contains section 4.3 nodes sort and remove the 4.4 Section cutter Section 4.5 attribute selector for whitespace characters matching policy Section 4.6 Decomposition and matching of sub-element filtering pseudo-class section 5th Sizzle Engine 7th Chapter node module 1th point of Creation 2nd point of insertion 3rd points of replication 4th node of the Migration 5th section InnerHTML, InnerText and outerhtml of the processing 6th section Some wonderful elements node section 6.1 IFRAME 6.2 section Object 6.3 section video 8th data cache system 1th jquery 1th Generation Cache System 2nd section jquery 2nd cache system 3rd Section mass   1th generation data caching system for the Framework 4th section mass framework 2nd generation Data Cache System 5th Section mass framework 3rd generation data Cache System 9th Chapter style Module 1th section body structure 2nd section Style name Correction 3rd section Special handling of individual Styles section 3.1 Transparency section 3.2 user-select Section 3.3 backgroundposition Section 3.4 z-index section 3.5 Box Model section 3.6 section ElementThe dimensions of the elements section 3.7 of the element show the coordinates of section 3.8 elements of the 4th section of the scroll bars of the coordinates of the 10th Chapter Property Module Section 1th How to distinguish between intrinsic properties and custom properties 2nd section How to determine whether the browser distinguishes between intrinsic properties and custom attributes 3rd section IE's property System three evolution 4th section class The 5th section of the Prototype.js property system of the name is section 6th jquery property System 7th section Mass Framework property system 11th Chapter Event System 1th section onxxx bind way Defect 2nd Section attachevent defect 3rd Section Addev  Entlistener defect 4th Section Dean Edward's Addevent.js Source Analysis Section 5th jquery1.8.2 Event Module Overview 6th section jQuery.event.add Source code Interpretation 7th section JQuery.event.remove Source Interpretation 8th Section JQuery.event.dispatch Source Interpretation 9th Section JQuery.event.trigger Source interpretation 10th Section JQuery Fix Event object 11th section Repair of Wheel Events section 12th MouseEnter and repair of MouseLeave events section 13th Focusin fixes with Focusout events 14th section Implementation of event proxy for legacy IE under submit 15th section Oninput Event compatibility handling 12th Chapter Asynchronous processing 1th Section settimeout and setinterval 2nd section mochikit deferred 3rd section jsdeferred 4th section jQuery deferred 5th section JavaScript Asynchronous processing foreground 13th chapter Data interaction Module 1th AJAX Overview 2nd section gracefully get XMLHttpRequest Object 3rd section XMLHttpRequest object event binding and State Maintenance 4th section send request with Data 5th section receive data 6th section upload file 7th section A complete AJAX implementation 14th Chapter Animation engine 1th Section Animation principle 2nd section easing formula 3rd Section API Design 4th section mass Framework JS-based Animation engine 5th section requestanimationframe 6th Section CSS3 transition 7th Section CSS3 Animation 8th section mass framework CSS-based animation engine Chapter 15th plug-in section 1th jquery plug-in general notation 2nd section jquery UI action on inner class 3rd section JquerY Easyui Intelligent Loading and individualization 4th section more directly manipulate UI instances 16th. MVVM 1th Section Current mainstream MVVM framework Introduction 2nd section Property Change Listener 3rd Section ViewModel 4th section Binding 5th Section Monitoring array and sub-template epilogue 

Reading order, in principle there is no requirement, but the 2nd Chapter, 6th Chapter, 14th Chapter, 16th Chapter is very challenging, we can postpone reading. If the foundation is not very good, you can start from the 3rd chapter, skip the more difficult chapters I said. The book has been written to write a front-end framework needs to grasp the knowledge points and the details of all excavated out, the rest is on your good fortune. In short, as soon as possible to form their own knowledge tree, in order to single side.

The direction of the way is not the direction is blindfolded donkey in situ one year experience mixed ten years said is very good. You must paste the copy down article (Masaki)