A
A
Artyom Starchenko2015-06-14 16:23:17
JavaScript
Artyom Starchenko, 2015-06-14 16:23:17

What to use as an advanced JavaScript templating engine?

At the moment I have projects with a lot of client-side javascript code. I don't use frameworks, because at a certain point, the requirements of the architecture start to conflict with the capabilities of the frameworks and you have to fight. Now the architecture is built on TypeScript classes. However, this is not the issue.
At the moment, I use handlebars as a templating engine. But handlebars itself is stupid, and thinking about rendering templates takes a lot of work. I have two problems with it:
1) If you need to change only part of the template, then in order not to re-render everything, you have to break the templates into parts and manage the change in the desired part manually.
2) JS for the active interface (tabs, drop-down menus, sliders, etc.) is not clear how to store it normally, it does not fit well into the overall application architecture.
Is there some way to work with templates that completely or partially cures this problem, but does not require redesigning the entire application architecture to meet the requirements of some framework?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
N
Nikolay Talanov, 2015-06-14
@Starche

https://muut.com/riotjs/ - check this out.

F
Finnish, 2015-06-14
@finnish

React.js is positioned as an advanced templating engine with the ability to split a project into components. The developers assure, and I know from my own experience that its integration with an existing project is easy and requires a minimum of effort. And if Flux is also "fastened", then React will reveal itself in the best possible way.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question