Eight ways to optimize JavaScript code-headlines-php.cn

There are many ways to write the same effect in js code. There are many examples where the result can be the same but the steps are different. However, although you have written the effect, the performance of the page has been greatly reduced. Today's development and script performance improvement is becoming increasingly important. This article mainly shares with you an 8-point summary of JavaScript code optimization. I hope it can help you.

This article will introduce in detail several key points of JS programming style

Loose coupling

Loose coupling is achieved when one component is modified without changing other components. Coupling

1. Separate JS from CSS: Do not use CSS expressions

//不好的做法
.box{width: expression(document.body.offsetWidth + &#39;px&#39;)}

Copy after login

2. Separate CSS from JS : When modifying CSS style through JS, use className or classList instead of modifying style one by one.

//不好的做法一
ele.style.color = &#39;red&#39;;
ele.style.left= &#39;10px&#39;;
//不好的做法二
ele.style.cssText =&#39;color:red;left:10px;&#39;;

Copy after login

.reveal{color:red;left:10px;}
//好的做法一
ele.className += &#39;reveal&#39;;
//好的做法二
ele.classList.add(&#39;reveal&#39;);

Copy after login

3. Extract JS from HTML: Put the JS file into an external file

4. Extract HTML from JS: Do not splice the DOM structure in innerHTML, but use a string template. Such as handlebars

Global variables

Creating global variables is considered a bad practice, especially in the context of team development, which is particularly problematic. As the amount of code increases, global variables will cause some very important maintainability problems. The more global variables, the higher the probability of introducing errors

Generally speaking, there are three solutions:

1. Zero global variables

The implementation method is to use an immediate call function IIFE and place all scripts in it

(function(){
 var doc = win.document;
})(window);

Copy after login

The usage scenarios of this mode are limited. As long as the code needs to be dependent on other codes, or needs to be continuously expanded or modified during operation, this method cannot be used.

2. Single global variable and namespace

Rely on as few global variables as possible, that is, only create one global variable, use single variable mode, such as YUI or jQuery

Single global variable, that is, the only global object name created is Unique and mount all functional code to this global object. Therefore, each possible global variable becomes an attribute of a unique global variable, so that multiple global variables are not created.

A namespace is simply a functional grouping represented by a single attribute of the global object. For example, all methods under Y.DOM are related to DOM operations, and all methods under Y.Event are related to events. A common convention is that each file declares its own namespace through a new global object

3. Using modules

The module is a general functional fragment, it does not create a new global variables or namespace. Instead, all this code is stored in a single function that performs a task or publishes an interface. You can use a name to represent this module, and this module can also rely on other modules

Event processing

Couples event processing-related code with the event environment, resulting in poor maintainability

1. Isolate application logic

It is a best practice to separate application logic from all event handlers and separate application logic and event processing code

//不好的做法
function handleClick(event){
 var popup = document.getElementById(&#39;popup&#39;);
 popup.style.left = event.clientX + &#39;px&#39;;
 popup.style.top = event.clientY + &#39;px&#39;;
 popup.className = &#39;reveal&#39;;
}
addListener(element,&#39;click&#39;,handleClick);
//好的做法
var MyApplication = {
 handleClick: function(event){
  this.showPopup(event);
 },
 showPopup: function(event){
  var popup = document.getElementById(&#39;popup&#39;);
  popup.style.left = event.clientX + &#39;px&#39;;
  popup.style.top = event.clientY + &#39;px&#39;;
  popup.className = &#39;reveal&#39;;
 }
};
addListener(element,&#39;click&#39;,function(event){
 MyApplication.handleClick(event);
});

Copy after login

#2. Do not distribute event objects

Application logic should not rely on event objects to complete functions correctly. The method interface should indicate which data is necessary . Unclear code can lead to bugs. The best way is to let the event handler use the event object to handle the event, and then get all the required data and pass it to the application logic

//改进的做法
var MyApplication = {
 handleClick: function(event){
  this.showPopup(event.clientX,event.clientY);
 },
 showPopup: function(x,y){
  var popup = document.getElementById(&#39;popup&#39;);
  popup.style.left = x + &#39;px&#39;;
  popup.style.top = y + &#39;px&#39;;
  popup.className = &#39;reveal&#39;;
 }
};
addListener(element,&#39;click&#39;,function(event){
 MyApplication.handleClick(event);
});

Copy after login

When handling the event , it is best to make the event program the only function that touches the event object. The event handler should perform any necessary operations on the event object before entering the application logic, including preventing the event from bubbling, and should be included directly in the event handler

//改进的做法
var MyApplication = {
 handleClick: function(event){
  event.preventDefault();
  event.stopPropagation();
  this.showPopup(event.clientX,event.clientY);
 },
 showPopup: function(x,y){
  var popup = document.getElementById(&#39;popup&#39;);
  popup.style.left = x + &#39;px&#39;;
  popup.style.top = y + &#39;px&#39;;
  popup.className = &#39;reveal&#39;;
 }
};
addListener(element,&#39;click&#39;,function(event){
 MyApplication.handleClick(event);
});

Copy after login

Configuration data

Code is nothing more than defining a collection of instructions for the computer to execute. We often pass data into the computer, operate the data by instructions, and finally produce a result. When data has to be modified, some unnecessary risks may arise. Key data should be extracted from the code

Configuration data is a value that is hard-coded in the application and may be modified in the future, including the following content

1、URL
2、需要展现给用户的字符串
3、重复的值
4、配置项
5、任何可能发生变更的值

Copy after login

The following is the method of unprocessed configuration data

//不好的做法
function validate(value){
 if(!value){
  alert(&#39;Invalid value&#39;);
  location.href="/errors/invalid.php" rel="external nofollow" ;
 }
}
function toggleSelected(element){
 if(hasClass(element,&#39;selected&#39;)){
  removeClass(element,&#39;selected&#39;);
 }else{
  addClass(element,&#39;selected&#39;);
 }
}

Copy after login

The following code saves the configuration data in the config object. The config object Each attribute saves a data fragment, and each attribute name has a prefix to indicate the type of data (MSG indicates the information displayed to the user, URL indicates the network address, and CSS indicates that this is a className). Of course, you can also put the entire config object in a separate file, so that modifications to the configuration data can be completely isolated from the code that uses this data

//好的做法
var config = {
 MSG_INVALID_VALUE: &#39;Invalid value&#39;,
 URL_INVALID:&#39;/errors/invalid.php&#39;,
 CSS_SELECTED:&#39;selected&#39;
}
function validate(value){
 if(!value){
  alert(config.MSG_INVALID_VALUE);
  location.href=config.URL_INVALID;
 }
}
function toggleSelected(element){
 if(hasClass(element,config.CSS_SELECTED)){
  removeClass(element,config.CSS_SELECTED);
 }else{
  addClass(element,config.CSS_SELECTED);
 }
}

Copy after login

Selector optimization

Concentrate the elements selected by the selector as static attributes of the object into one place for unified management

initializeElements: function() {
  var eles = app.Eles;
  for (var name in eles) {
    if (eles.hasOwnProperty(name)) {
      this[name] = $(eles[name]);
    }
  }
}

Copy after login

The following is one Example

//好的做法app.Eles = {
  widgetp: ".left-widget p",
  inputResize: &#39;.input-resize&#39;,
  hr: &#39;.hr&#39;,
  txt: &#39;.input-group-btn button&#39;,
  cus: &#39;#paper-type-cus&#39;,
  hid: &#39;#hidden&#39;,
  mainCon: &#39;#mainCon&#39;,
  rulerX: &#39;.ruler-x&#39;,
  rulerY: &#39;.ruler-y&#39;,
};

Copy after login

Function optimization

[Refined function]

在javascript开发中，大部分时间都在与函数打交道，所以希望这些函数有着良好的命名，函数体内包含的逻辑清晰明了。如果一个函数过长，不得不加上若干注释才能让这个函数显得易读一些，那这些函数就很有必要进行重构

如果在函数中有一段代码可以被独立出来，那最好把这些代码放进另外一个独立的函数中。这是一种很常见的优化工作，这样做的好处主要有以下几点

1、避免出现超大函数

2、独立出来的函数有助于代码复用

3、独立出来的函数更容易被覆写

4、独立出来的函数如果拥有一个良好的命名，它本身就起到了注释的作用

比如在一个负责取得用户信息的函数里面，还需要打印跟用户信息有关的log，那么打印log的语句就可以被封装在一个独立的函数里：

var getUserInfo = function(){
  ajax( &#39;http:// xxx.com/userInfo&#39;, function( data ){
    console.log( &#39;userId: &#39; + data.userId );
    console.log( &#39;userName: &#39; + data.userName );
    console.log( &#39;nickName: &#39; + data.nickName );
  });
};
//改成：
var getUserInfo = function(){
  ajax( &#39;http:// xxx.com/userInfo&#39;, function( data ){
    printDetails( data );
  });
};
var printDetails = function( data ){
  console.log( &#39;userId: &#39; + data.userId );
  console.log( &#39;userName: &#39; + data.userName );
  console.log( &#39;nickName: &#39; + data.nickName );
};

Copy after login

【尽量减少参数数量】

如果调用一个函数时需要传入多个参数，那这个函数是让人望而生畏的，必须搞清楚这些参数代表的含义，必须小心翼翼地把它们按照顺序传入该函数。在实际开发中，向函数传递参数不可避免，但应该尽量减少函数接收的参数数量。下面举个非常简单的示例。有一个画图函数draw，它现在只能绘制正方形，接收了3个参数，分别是图形的width、heigth以及square：

var draw = function(width,height,square){};

Copy after login

但实际上正方形的面积是可以通过width和height计算出来的，于是我们可以把参数square从draw函数中去掉：

var draw = function( width, height ){
  var square = width * height;
};

Copy after login

假设以后这个draw函数开始支持绘制圆形，需要把参数width和height换成半径radius，但图形的面积square始终不应该由客户传入，而是应该在draw函数内部，由传入的参数加上一定的规则计算得来。此时，可以使用策略模式，让draw函数成为一个支持绘制多种图形的函数

【传递对象参数代替过长的参数列表】

有时候一个函数有可能接收多个参数，而参数的数量越多，函数就越难理解和使用。使用该函数的人首先得搞明白全部参数的含义，在使用的时候，还要小心翼翼，以免少传了某个参数或者把两个参数搞反了位置。如果想在第3个参数和第4个参数之中增加一个新的参数，就会涉及许多代码的修改，代码如下：

var setUserInfo = function( id, name, address, sex, mobile, qq ){
  console.log( &#39;id= &#39; + id );
  console.log( &#39;name= &#39; +name );
  console.log( &#39;address= &#39; + address );
  console.log( &#39;sex= &#39; + sex );
  console.log( &#39;mobile= &#39; + mobile );
  console.log( &#39;qq= &#39; + qq );
};
setUserInfo( 1314, &#39;xiaohuochai&#39;, &#39;beijing&#39;, &#39;male&#39;, &#39;150********&#39;, 121631835 );

Copy after login

这时可以把参数都放入一个对象内，然后把该对象传入setUserInfo函数，setUserInfo函数需要的数据可以自行从该对象里获取。现在不用再关心参数的数量和顺序，只要保证参数对应的key值不变就可以了：

var setUserInfo = function( obj ){
    console.log( &#39;id= &#39; + obj.id );
    console.log( &#39;name= &#39; + obj.name );
    console.log( &#39;address= &#39; + obj.address );
    console.log( &#39;sex= &#39; + obj.sex );
    console.log( &#39;mobile= &#39; + obj.mobile );
    console.log( &#39;qq= &#39; + obj.qq );
  };
  setUserInfo({
    id: 1314,
    name: &#39;xiaohuochai&#39;,
    address: &#39;beijing&#39;,
    sex: &#39;male&#39;,
    mobile: &#39;150********&#39;,
    qq: 121631835
  });

Copy after login

条件优化

【合并条件片段】

如果一个函数体内有一些条件分支语句，而这些条件分支语句内部散布了一些重复的代码，那么就有必要进行合并去重工作。假如有一个分页函数paging，该函数接收一个参数currPage，currPage表示即将跳转的页码。在跳转之前，为防止currPage传入过小或者过大的数字，要手动对它的值进行修正，详见如下伪代码：

var paging = function( currPage ){
  if ( currPage <= 0 ){
    currPage = 0;
    jump( currPage ); // 跳转
  }else if ( currPage >= totalPage ){
    currPage = totalPage;
    jump( currPage ); // 跳转
  }else{
    jump( currPage ); // 跳转
  }
};

Copy after login

可以看到，负责跳转的代码jump(currPage)在每个条件分支内都出现了，所以完全可以把这句代码独立出来：

var paging = function( currPage ){
  if ( currPage <= 0 ){
    currPage = 0;
  }else if ( currPage >= totalPage ){
    currPage = totalPage;
  }
  jump( currPage ); // 把jump 函数独立出来
};

Copy after login

【把条件分支语句提炼成函数】

在程序设计中，复杂的条件分支语句是导致程序难以阅读和理解的重要原因，而且容易导致一个庞大的函数。假设现在有一个需求是编写一个计算商品价格的getPrice函数，商品的计算只有一个规则：如果当前正处于夏季，那么全部商品将以8折出售。代码如下：

var getPrice = function( price ){
  var date = new Date();
  if ( date.getMonth() >= 6 && date.getMonth() <= 9 ){ // 夏天
    return price * 0.8;
  }
  return price;
};

Copy after login

观察这句代码：

date.getMonth()>=6&&date.getMonth()<=9

Copy after login

这句代码要表达的意思很简单，就是判断当前是否正处于夏天（7~10月）。尽管这句代码很短小，但代码表达的意图和代码自身还存在一些距离，阅读代码的人必须要多花一些精力才能明白它传达的意图。其实可以把这句代码提炼成一个单独的函数，既能更准确地表达代码的意思，函数名本身又能起到注释的作用。代码如下：

var isSummer = function(){
  var date = new Date();
  return date.getMonth() >= 6 && date.getMonth() <= 9;
};
var getPrice = function( price ){
  if ( isSummer() ){ // 夏天
    return price * 0.8;
  }
  return price;
};

Copy after login

【提前让函数退出代替嵌套条件分支】

许多程序员都有这样一种观念：“每个函数只能有一个入口和一个出口。”现代编程语言都会限制函数只有一个入口。但关于“函数只有一个出口”，往往会有一些不同的看法。下面这段伪代码是遵守“函数只有一个出口的”的典型代码：

var del = function( obj ){
  var ret;
  if ( !obj.isReadOnly ){ // 不为只读的才能被删除
    if ( obj.isFolder ){ // 如果是文件夹
      ret = deleteFolder( obj );
    }else if ( obj.isFile ){ // 如果是文件
      ret = deleteFile( obj );
    }
  }
  return ret;
};

Copy after login

嵌套的条件分支语句绝对是代码维护者的噩梦，对于阅读代码的人来说，嵌套的if、else语句相比平铺的if、else，在阅读和理解上更加困难。嵌套的条件分支往往是由一些深信“每个函数只能有一个出口的”程序员写出的。但实际上，如果对函数的剩余部分不感兴趣，那就应该立即退出。引导阅读者去看一些没有用的else片段，只会妨碍他们对程序的理解

于是可以挑选一些条件分支，在进入这些条件分支之后，就立即让这个函数退出。要做到这一点，有一个常见的技巧，即在面对一个嵌套的if分支时，可以把外层if表达式进行反转。重构后的del函数如下：

var del = function( obj ){
  if ( obj.isReadOnly ){ // 反转if 表达式
    return;
  }
  if ( obj.isFolder ){
    return deleteFolder( obj );
  }
  if ( obj.isFile ){
    return deleteFile( obj );
  }
};

Copy after login

循环优化

【合理使用循环】

在函数体内，如果有些代码实际上负责的是一些重复性的工作，那么合理利用循环不仅可以完成同样的功能，还可以使代码量更少。下面有一段创建XHR对象的代码，为了简化示例，只考虑版本9以下的IE浏览器，代码如下：

var createXHR = function(){
  var xhr;
  try{
    xhr = new ActiveXObject( &#39;MSXML2.XMLHttp.6.0&#39; );
  }catch(e){
    try{
      xhr = new ActiveXObject( &#39;MSXML2.XMLHttp.3.0&#39; );
    }catch(e){
      xhr = new ActiveXObject( &#39;MSXML2.XMLHttp&#39; );
    }
  }
  return xhr;
};
var xhr = createXHR();

Copy after login

下面灵活地运用循环，可以得到跟上面代码一样的效果：

//下面我们灵活地运用循环，可以得到跟上面代码一样的效果：
var createXHR = function(){
  var versions= [ &#39;MSXML2.XMLHttp.6.0ddd&#39;, &#39;MSXML2.XMLHttp.3.0&#39;, &#39;MSXML2.XMLHttp&#39; ];
  for ( var i = 0, version; version = versions[ i++ ]; ){
    try{
      return new ActiveXObject( version );
    }catch(e){
    }
  }
};
var xhr = createXHR();

Copy after login

【用return退出多重循环】

假设在函数体内有一个两重循环语句，需要在内层循环中判断，当达到某个临界条件时退出外层的循环。大多数时候会引入一个控制标记变量：

var func = function(){
  var flag = false;
  for ( var i = 0; i < 10; i++ ){
    for ( var j = 0; j < 10; j++ ){
      if ( i * j >30 ){
        flag = true;
        break;
      }
    }
    if ( flag === true ){
      break;
    }
  }
};

Copy after login

第二种做法是设置循环标记：

var func = function(){
  outerloop:
  for ( var i = 0; i < 10; i++ ){
    innerloop:
    for ( var j = 0; j < 10; j++ ){
      if ( i * j >30 ){
        break outerloop;
      }
    }
  }
};

Copy after login

这两种做法无疑都让人头晕目眩，更简单的做法是在需要中止循环的时候直接退出整个方法：

var func = function(){
  for ( var i = 0; i < 10; i++ ){
    for ( var j = 0; j < 10; j++ ){
      if ( i * j >30 ){
        return;
      }
    }
  }
};

Copy after login

当然用return直接退出方法会带来一个问题，如果在循环之后还有一些将被执行的代码呢？如果提前退出了整个方法，这些代码就得不到被执行的机会：

var func = function(){
  for ( var i = 0; i < 10; i++ ){
    for ( var j = 0; j < 10; j++ ){
      if ( i * j >30 ){
        return;
      }
    }
  }
  console.log( i ); // 这句代码没有机会被执行
};

Copy after login

为了解决这个问题，可以把循环后面的代码放到return后面，如果代码比较多，就应该把它们提炼成一个单独的函数：

var print = function( i ){
  console.log( i );
};
var func = function(){
  for ( var i = 0; i < 10; i++ ){
    for ( var j = 0; j < 10; j++ ){
      if ( i * j >30 ){
        return print( i );
      }
    }
  }
};func();

Copy after login