自然科普专题收录与推荐标准请参考: https://www.jianshu.com/p/e38bf5116797 如因为一些可改动的问题被拒稿，请在修改后简信联系主编：刷牙喝凉白开，主编审核后将收录符合要求的文章；如在了解收录标准后仍对拒稿有异议，也可简信联系主编。 《自然科普月刊》将恢复发刊，欢迎大家踊跃投稿，投稿可发链接给主编。 专题长期招募副编。副编招募信息见下： https://www.jianshu.com/p/9d116265ccc1

少一点套路，多一点真诚~

爱技术，爱读书，生命不断，学习不止。

When working on a web application that involves a lot of JavaScript, one of the first things you learn is to stop tying your data to the DOM. It's all too easy to create JavaScript applications that end up as tangled piles of jQuery selectors and callbacks, all trying frantically to keep data in sync between the HTML UI, your JavaScript logic, and the database on your server. For rich client-side applications, a more structured approach is often helpful. With Backbone, you represent your data as Models, which can be created, validated, destroyed, and saved to the server. Whenever a UI action causes an attribute of a model to change, the model triggers a "change" event; all the Views that display the model's state can be notified of the change, so that they are able to respond accordingly, re-rendering themselves with the new information. In a finished Backbone app, you don't have to write the glue code that looks into the DOM to find an element with a specific id, and update the HTML manually — when the model changes, the views simply update themselves. Philosophically, Backbone is an attempt to discover the minimal set of data-structuring (models and collections) and user interface (views and URLs) primitives that are generally useful when building web applications with JavaScript. In an ecosystem where overarching, decides-everything-for-you frameworks are commonplace, and many libraries require your site to be reorganized to suit their look, feel, and default behavior — Backbone should continue to be a tool that gives you the freedom to design the full experience of your web application.

工作中使用了backbone，记录下来交流backbone的使用经验

笔耕生活点绩

收集Vue文章，资料，和社区问题。社区问题会整理最佳回答和笔者的一些见解。 欢迎投稿。 qq群：240319632