there is no need to buy books. It is recommended to take a look at the online interpretation of Vue, which will certainly benefit you a lot. " share a detailed and easy-to-understand vue2.0 source code analysis "

first look at the software documentation to understand what the software does, then look at the architecture of the project, and then look at the modules according to the architecture, and then you need to be very familiar with the language implemented by the project. When you sort out each module, open the editor. Copy the source code according to the author's idea, and then try to understand why it is written this way, and then copy it and you will find, shit. So that's how it works. I'll write a better one to do it, and of course you'll be amazed, fuck... How can the author even think of this, awesome, and then you will enter the author's mind, enjoy the fun of this work, of course, you can also use a pen to copy the source code in the book, which is more impressive. no, no, no.

personal experience, if you want to understand the source code of a project, the best way is not to read, but to see what functions the project has achieved and build a wheel that is the simplest to implement. In the process of building wheels, you will directly feel which ideas in the source code are worth learning, where your ideas are lacking, and where they are better than the author. With an in-depth understanding of the source code of a project, you can also communicate directly with the author. This approach is more useful for personal improvement than reading 10 books.