Go deep into the V8. – Write it up front

This post is not going to talk about technology, but something else. The main reason for writing this post is to read my blog’s signature and say something before starting the final source series.

I am a career changer in front end, previously doing game operations.

Each sentence above is a very difficult process, as a 211 master, after graduation, nothing, wasted about a year before deciding to switch to technology, in order to make up for the wasted year, paid too much.

I was interested in source code when I was in pre-school, when I was reading Query3.1, and I was almost dissuaded by the Sizzle engine because it was a bit naive to study it just because I knew the syntax.

I was happy when I got my first job. Although the salary was very low, there was not much work to do. I could build up my confidence and have time to study my own things. At that time spent a full half a year to run vUE source code, I look at the source code method is more special, and do not recommend. The first time is to copy, line by line, and then comment on the tool methods. The second time, I made a breakpoint in the new Vue and saw the entire code flow from beginning to end. Finally stumbled is also finished, but the quality of not polite to say, is rubbish, may be in addition to my own no one can understand. But what the hell, writing it down is progress.

The Webpack source code is one of the less successful options. It was a great tool, and I was so impressed by it that I became very interested in how it was implemented. But when I delve deeper, I find that the code is extremely unreadable, full of methods I don’t know, backward compatibility, OS compatibility, and sometimes I write a post full of code I don’t know what to say. Finally, it is a relief to abandon the pit, no one on the market is still reasonable.

In this way, the first year passed, and I also read the JRE data structure, express source code, and so on.

The next year, I set a new goal, looking at the Node source code. I don’t remember what triggered this decision, either because of the chance to compile Node in VS, the moment I saw the REPL, or because I wanted to see V8 build a stepping stone. Anyway, here we go. However, unfortunately, node source itself really no nutrition, it is like a 502, V8 and Libuv stuck together, Node source code eventually became libuv source code. This series of writing is not much, equivalent to just polling the event again, the middle indulged in games, indulged in gambling, and even accidentally into the headlines, in order to adapt to work pigeons for a long time. Finally in the previous period of time idle down, to fill the hole.

Today is May 22, 19, my first job started on March 27, 17, which has been more than two years.

The V8 engine learned JavaScript thinking that one day I would kill it, and now it has finally come to that point. But to be honest, this is a very difficult goal, far more than any source code I’ve seen before. There are not many people studying this thing in China, and there are few references. And look at the V8 engine. To be honest, it’s basically useless for interviews except for bullshit, and the front end is unlikely to touch C++ for the most part. On the business side, since there is generally no complex logic, knowing the underlying principles of V8 doesn’t bother to do anything for a little optimization. That is to say, I can only do this by pure interest. I hope it won’t be like the red Black tree article, which will be dishonored.

I don’t know how much I will write about this series, how I will write about this series, whether I will write about this series. But as the end goal of my front-end, I hope to have some output.

If the V8 engine is an ocean, I’m a lonely boat, exploring mysterious places and searching for the treasure of my mind.

I’ll tell you what. Finally, wish V8. I hope I have a good date. Bless me.