Case Analysis of javascript algorithm

This article mainly introduces the relevant knowledge of javascript algorithm case analysis, the content is detailed and easy to understand, the operation is simple and fast, and has a certain reference value. I believe you will gain something after reading this javascript algorithm case analysis article. Let's take a look at it.

First open the page:

I've said this once before, and now I'm going to talk about other ways to get around it.

The first is the conditional breakpoint, that is, if the condition is met, it will be broken, and if it is not satisfied, it will be skipped.

The second is to keep going down, that is to say, if this line is set up, it will not be broken.

The premise of these two operations is that js will not change, because Google's V8 engine optimizes js. If it is the same js, it will be executed as one, so the loop is generated.

(function () {var a = new Date (); debugger; return new Date ()-a > 100;} ())

That is really useless, will optimize the first generation, unless you generate different each time we analyze everyone from the engine point of view suddenly enlightened.

Now we ban both places, and then we look at the home page instead, and we start from the beginning.

We see that he will load a piece of js and then execute the following paragraph, and we see that there is another one on it.