When comparing swig vs Pure.js, the Slant community recommends swig for most people. In the question“What are the best JavaScript templating engines?” swig is ranked 14th while Pure.js is ranked 28th. The most important reason people chose swig is:
Available for node.js and major web browsers
Ranked in these QuestionsQuestion Ranking
Pros
Pro Works both on the client and on the server
Available for node.js and major web browsers
Pro Does not hide HTML
Swig does not abstract HTML syntax from you (like e.g. Jade does) giving a certain filling of control over the markup.
Pro Automatically extends JavaScript libraries available
If a Javascript library is available in the page when it's loaded, Pure will automatically extend it to use it inside the templates.
Cons
Con No updates for at least 6 months
Swig has not received any new commits since June 25 2015.

Con Injection not explicit in template
Looking at the template, we cannot see where content will be injected. Instead, all we see are empty tags.

Con Not enough separation
The controller knows too much about the template.
Con Not many reasources outside the official documentation
PureJS is not very popular and it's not used by many. Because of this, there are not many guides or tutorials out there for Pure.js other than the official documentation.
