Why did Google create another template system for its AJAX applications instead of using an existing solution?
There are many reasons why we created a new solution: • Better performance. We wanted JavaScript templates that aren’t parsed on the client. Closure Templates compiles the templates server-side into efficient JavaScript functions, which can then be rendered client-side. • One template for client and server code. We wanted templates that have a language-neutral syntax such that you can write a template once and reuse it from both server-side Java and client-side JavaScript. With Closure Templates, you can render your application’s initial UI server-side and then have the client-side JavaScript modify specific parts of the UI by re-rendering some of the templates that make up parts of the page. • Natural for programmers. We wanted a template syntax that was comfortable for programmers, without the limitations of XML-based syntax. Closure Templates give programmers the ability to have many templates in the same source file and for templates to call each other like functions. • Easy-to-use
Related Questions
- Sometimes it would be desirable if one could use existing mainframe programs in WINDOWS or UNIX/LINUX/Linux on System z applications. Can we use tcACCESS to integrate the mainframe programs?
- HOW DO I FIND OUT THE SOLUTION PERCENTAGE (GLYCOL FREEZE POINT) OF AN EXISTING SYSTEM?
- Can I create RECs by adding additional panels to an existing photovoltaic system?
