<%=title%> - Page Test

[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8},"actionData","errors","root",{"_11":-5},"routes/user.$name.topics",{"_9":10,"_11":12,"_13":14,"_15":16,"_17":18,"_19":16},"topics",[35],"user",{"_20":21,"_13":14,"_22":23,"_24":25,"_26":27,"_28":29,"_30":16,"_31":32,"_33":34},"loginname","ejialin","page",1,"limit",20,"total","id","6137","avatar_url","http://www.gravatar.com/avatar/d16b0c314f3e7b6bd6eef59324bcd544?size=48","githubUsername","","create_at","2013-01-04 17:02:46.343","score",5,"topic_count","reply_count",0,"is_star",false,{"_20":36,"_37":21,"_38":39,"_40":41,"_42":43,"_44":45,"_46":34,"_47":34,"_31":48,"_49":50,"_26":51,"_52":53},"2304","author_id","tab","share","content","在刚刚入门 Node.js，在考虑使用哪个模板时，简单的以1万行数据，进行解释效率比较：\r\nJade 模板：\r\n\r\n\r\n !!!\r\n html\r\n \thead\r\n \t\ttitle #{title}\r\n \t\tmeta(charset=\"UTF-8\")\r\n \tbody\r\n \t\tdiv.description #{description}\r\n \t\tul\r\n \t\t\t- each data in datas\r\n \t\t\t\tli.item(id='item_'+data.index)\r\n \t\t\t\t\tspan= data.time\r\n \t\t\t\t\ta.art(href=data.url)= data.title\r\n\r\nejs 模板：\r\n\r\n \r\n \r\n \r\n \t\r\n \t<%=title%> - Page Test\r\n \r\n \r\n \t

<%=description%>

\r\n \t

\"><%=data.time%>\" class=\"art\"><%=data.title%>

\r\n \r\n \r\n \r\n\r\nHandlebars 模板：\r\n\r\n\r\n \r\n \r\n \r\n \t\r\n \t{{title}} - Page Test\r\n \r\n \r\n \t

\r\n \t

{{time}}{{title}}

\r\n \r\n \r\n \r\n\r\n效率比较结果（平均消耗时间，约数）\r\n**Jade 287ms > ejs 43ms > Handlebars 28ms**\r\n\r\nJade 因为采用了类似 zen coding 的语法，比较新奇，但效率极其低下。如果只保留 `

` 部分的1万行数据解释，则约为245ms。\r\n综上所述，对 Jade，我个人不建议，除了效率，另外一个主要原因是可视化太弱，甚至可以说是毫无可视化可言，学习成本高，维护与团队合作成本高，语法过于晦涩、复杂。\r\n\r\n**最新更新：**\r\n根据 [@jiyinyiyong](/user/jiyinyiyong) 提供的资料，找到 http://jsperf.com/dom-vs-innerhtml-based-templating/413#status\r\n并同样测试了 doT，速度约为**15ms**，为目前最快，而且提供了相对全面的模板语法：http://olado.github.com/doT/","title","Web 模板 Jade、EJS、Handlebars 万行代码解释效率比较，Jade 完败","last_reply_at","2017-03-08 06:43:01.451","good","top",83,"visit_count",101335,"2013-01-04 17:18:23.927","author",{"_13":14,"_22":23}]