anchor.diff:    of information about how to write and organize Angular code - and equally
     importantly - how **not** to write and organize Angular code.
   
  -  [Angular风格指南](https://github.com/johnpapa/angular-styleguide)收集了一些
  -  已证明能写出干净且可维护的Angular 1程序的模式与实践。
  -  它包含了很多关于如何书写和组织Angular代码的有价值信息，同样重要的是，**不应该**如何书写和组织Angular代码。
  +  [Angular风格指南](https://github.com/johnpapa/angular-styleguide)收集了一些已证明能写出干净且可维护的Angular 1程序的模式与实践。
  +  它包含了很多关于如何书写和组织Angular代码的有价值信息，同样重要的是，**不应该**采用的书写和组织Angular代码的方式。
   
     Angular 2 is a reimagined version of the best parts of Angular 1. In that
     sense, its goals are the same as the Angular Style Guide's: To preserve
  
positive.code:     rules define similar principles on a higher level of abstraction: Different parts of the
      application should reside in different directories and Angular modules.
  
    * [按特性分目录的结构](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#folders-by-feature-structure)
      和[模块化](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#modularity)
      规则在较高的抽象层定义了一些相似的原则：应用程序中的不同部分应该被分到不同的目录和Angular模块中。
  
    When an application is laid out feature per feature in this way, it can also be
    migrated one feature at a time. For applications that don't already look like
  
negative.code:     them between languages and frameworks one at a time. In this example application,
      each controller, component, service, and filter is in its own source file.
  
    * [单一规则](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#single-responsibility)
      规定每个文件应该只放一个组件。这不仅让组件更容易浏览和查找，而且还将允许我们逐个迁移它们的语言和框架。
      在这个范例程序中，每个控制器、工厂和过滤器都在它自己的源文件中。
  
    * The [Folders-by-Feature Structure](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#folders-by-feature-structure)
  